Skip to content
Continuous Integration

Make wrong_permitted_algorithm test use a non-deprecated Hash #1650

Sign in to view logs

Make wrong_permitted_algorithm test use a non-deprecated Hash

Make wrong_permitted_algorithm test use a non-deprecated Hash #1650

Triggered via pull request August 31, 2023 14:47
@tgonzalezorlandoarmtgonzalezorlandoarm
opened #695
tgonzalezorlandoarm:tg/fix-wrong_permitted_algorithm
Status Failure
Total duration 45m 12s
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
9m 19s
Cross-compile Parsec to various targets
Check links
13s
Check links
Various tests targeting a Parsec image with all providers included
44m 46s
Various tests targeting a Parsec image with all providers included
Cargo check all-providers (current Rust stable & old compiler)
16m 19s
Cargo check all-providers (current Rust stable & old compiler)
Integration tests using Mbed Crypto provider
7m 57s
Integration tests using Mbed Crypto provider
Integration tests using PKCS 11 provider
9m 0s
Integration tests using PKCS 11 provider
Integration tests using TPM provider
9m 31s
Integration tests using TPM provider
Integration tests using Crypto Trusted Service provider
8m 26s
Integration tests using Crypto Trusted Service provider
Integration tests using CryptoAuthentication Library provider
7m 49s
Integration tests using CryptoAuthentication Library provider
Check that the fuzz testing framework is still working
20m 55s
Check that the fuzz testing framework is still working
OnDiskKIM E2E tests on all providers
43m 18s
OnDiskKIM E2E tests on all providers
Fit to window
Zoom out
Zoom in

Annotations

5 errors and 12 warnings
Integration tests using CryptoAuthentication Library provider
Process completed with exit code 101.
Integration tests using Mbed Crypto provider
Process completed with exit code 101.
Integration tests using Crypto Trusted Service provider
Process completed with exit code 101.
Integration tests using PKCS 11 provider
Process completed with exit code 101.
Integration tests using TPM 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/
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 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 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/
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/
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/
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/
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/