Skip to content
Continuous Integration

Update cryptoki and cryptoki-sys crates #1679

Sign in to view logs

Update cryptoki and cryptoki-sys crates

Update cryptoki and cryptoki-sys crates #1679

Triggered via pull request September 20, 2023 13:57
@tgonzalezorlandoarmtgonzalezorlandoarm
synchronize #697
tgonzalezorlandoarm:tg/update-cryptoki
Status Failure
Total duration 23m 24s
Artifacts –

ci.yml

on: pull_request
build-and-export-test-all-docker
0s
build-and-export-test-all-docker
Cross-compile Parsec to various targets
11m 5s
Cross-compile Parsec to various targets
Check links
14s
Check links
Various tests targeting a Parsec image with all providers included
15m 3s
Various tests targeting a Parsec image with all providers included
Cargo check all-providers (current Rust stable & old compiler)
23m 10s
Cargo check all-providers (current Rust stable & old compiler)
Integration tests using Mbed Crypto provider
15m 18s
Integration tests using Mbed Crypto provider
Integration tests using PKCS 11 provider
18m 14s
Integration tests using PKCS 11 provider
Integration tests using TPM provider
20m 5s
Integration tests using TPM provider
Integration tests using Crypto Trusted Service provider
17m 50s
Integration tests using Crypto Trusted Service provider
Integration tests using CryptoAuthentication Library provider
16m 41s
Integration tests using CryptoAuthentication Library provider
Check that the fuzz testing framework is still working
6m 43s
Check that the fuzz testing framework is still working
OnDiskKIM E2E tests on all providers
14m 10s
OnDiskKIM E2E tests on all providers
Fit to window
Zoom out
Zoom in

Annotations

4 errors and 12 warnings
Check that the fuzz testing framework is still working
Process completed with exit code 101.
OnDiskKIM E2E tests on all providers
Process completed with exit code 101.
Various tests targeting a Parsec image with all providers included
Process completed with exit code 101.
Integration tests using PKCS 11 provider
Process completed with exit code 101.
Check links
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Check links
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Check that the fuzz testing framework is still working
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Cross-compile Parsec to various targets
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
OnDiskKIM E2E tests on all providers
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Various tests targeting a Parsec image with all providers included
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Integration tests using Mbed Crypto provider
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Integration tests using CryptoAuthentication Library provider
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Integration tests using Crypto Trusted Service provider
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Integration tests using PKCS 11 provider
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Integration tests using TPM provider
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Cargo check all-providers (current Rust stable & old compiler)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/