Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Investigate e2e_tests failure on RasberryPi for PKCS11 backend #676

Open
gowthamsk-arm opened this issue May 23, 2023 · 0 comments
Open

Comments

@gowthamsk-arm
Copy link
Contributor

When e2e_tests are executed against the Nitrokey HSM, we see the following failures.

failures:
    per_provider::normal_tests::asym_encryption::asym_encrypt_and_decrypt_rsa_pkcs
    per_provider::normal_tests::asym_encryption::asym_encrypt_decrypt_rsa_pkcs_different_keys
    per_provider::normal_tests::asym_encryption::simple_asym_encrypt_rsa_oaep_pkcs11
    per_provider::normal_tests::asym_encryption::simple_asym_encrypt_rsa_pkcs
    per_provider::normal_tests::asym_sign_verify::asym_verify_fail_ecc_sha256
    per_provider::normal_tests::asym_sign_verify::fail_verify_hash2_ecc
    per_provider::normal_tests::asym_sign_verify::fail_verify_hash_ecc
    per_provider::normal_tests::asym_sign_verify::fail_verify_hash_rsa
    per_provider::normal_tests::asym_sign_verify::sign_verify_hash_ecc
    per_provider::normal_tests::asym_sign_verify::simple_verify_hash_ecc
    per_provider::normal_tests::capability_discovery::rsa_encrypt_use_check
    per_provider::normal_tests::export_public_key::check_public_ecc_export_format
    per_provider::normal_tests::export_public_key::import_and_export_ecc_public_key
    per_provider::normal_tests::export_public_key::import_and_export_ecc_public_key_by_export_public_key_fn
    per_provider::normal_tests::import_key::check_format_import_ecc
    per_provider::normal_tests::import_key::import_ecc_key
    per_provider::normal_tests::import_key::import_ecc_key_twice

test result: FAILED. 129 passed; 17 failed; 2 ignored; 0 measured; 2 filtered out; finished in 641.74s

As part of this issue, we need to understand the root cause and fix the failing tests.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant