-
Notifications
You must be signed in to change notification settings - Fork 17
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
EC tests failing #15
Comments
Thanks for problem report. PR #16 addresses the issue. For the test cases to work, you would need to have a CEX5C(*) adapter online:
I tested the fixed testcases on my systems. Does it work for you? If so, would you like to have it available via a 3.3.2 release ? (*) edit: (or newer) |
Tests are properly skipped now, thanks. Yes, a new release will be appreciated. BTW won't make sense to add a doc explaining what features what tests expect? I'm sure it would help our QA team when planning testing resources. |
The problem is fixed with the 3.3.2 release. We maintain a doc which lists the HW requirements of libica's interfaces here: However, for the testcases the situation is different, because most functions implement fallbacks to older HW or to SW (libcrypto), so a test might be expected to pass even if HW is not available. I ll keep this idea in mind for future releases: #17 |
Sounds good, and thanks for all updates :-) |
EC-related tests fail with recent libica in our guests (zEC12, z13), I suppose it's because the required HW is not available there. It my assumption is true, then the tests should use a check first like the SHA3 tests do and be "SKIP"-ed.
The failure messages are like
The text was updated successfully, but these errors were encountered: