Skip to content
Continuous Integration

Update cryptoki and cryptoki-sys crates #1684

Sign in to view logs

Update cryptoki and cryptoki-sys crates

Update cryptoki and cryptoki-sys crates #1684

Triggered via pull request September 20, 2023 22:20
@tgonzalezorlandoarmtgonzalezorlandoarm
synchronize #697
tgonzalezorlandoarm:tg/update-cryptoki
Status Failure
Total duration 20m 7s
Artifacts –
This run and associated checks have been archived and are scheduled for deletion. Learn more about checks retention

ci.yml

on: pull_request
build-and-export-test-all-docker
0s
build-and-export-test-all-docker
Cross-compile Parsec to various targets
9m 45s
Cross-compile Parsec to various targets
Check links
12s
Check links
Various tests targeting a Parsec image with all providers included
16m 47s
Various tests targeting a Parsec image with all providers included
Cargo check all-providers (current Rust stable & old compiler)
19m 30s
Cargo check all-providers (current Rust stable & old compiler)
Integration tests using Mbed Crypto provider
15m 22s
Integration tests using Mbed Crypto provider
Integration tests using PKCS 11 provider
15m 41s
Integration tests using PKCS 11 provider
Integration tests using TPM provider
19m 56s
Integration tests using TPM provider
Integration tests using Crypto Trusted Service provider
18m 23s
Integration tests using Crypto Trusted Service provider
Integration tests using CryptoAuthentication Library provider
16m 46s
Integration tests using CryptoAuthentication Library provider
Check that the fuzz testing framework is still working
9m 28s
Check that the fuzz testing framework is still working
OnDiskKIM E2E tests on all providers
15m 0s
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.
Integration tests using PKCS 11 provider
Process completed with exit code 101.
Various tests targeting a Parsec image with all providers included
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/
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 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 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/
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 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/
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/
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/