[cryptotest] Split Hash and HMAC tests into different bazel rules for each configuration #23518
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The tests for SHA2/SHA3/SHAKE and HMAC were each bundled into a single bazel rule for all configurations, which was causing timeout issues and making it difficult to debug specific failures. This PR splits the tests for these algorithms into separate bazel rules for each configuration. This provides better reliability w.r.t. timeouts at the expense of additional rounds of loading the test firmware to the test platform (FPGA or silicon).
Making this work required refactoring the manual tests for SHA3/SHAKE to only include one algorithm per file, and the HMAC NIST test vector parser to produce separate JSON files for each HMAC hash mode.