-
Notifications
You must be signed in to change notification settings - Fork 12
OpenTitan regression script bug fixes #166
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
Changes from all commits
8dba282
d171f72
d1cb726
0e9e1a9
67feaa2
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,26 @@ | ||
# OpenTitan regressions | ||
jwnrt marked this conversation as resolved.
Show resolved
Hide resolved
|
||
|
||
The `run-bazel-tests.sh` script and accompanying CI workflow allow us to run | ||
regression tests against the OpenTitan repository. Currently only Earlgrey tests | ||
are supported. | ||
|
||
With a checkout of OpenTitan, the script can be run like this: | ||
|
||
```sh | ||
./scripts/opentitan/run-bazel-tests.sh path/to/opentitan path/to/qemu | ||
``` | ||
|
||
The script will execute all QEMU-compatible tests using QEMU as it was built | ||
at the given path. The test results will be compared against two lists checked | ||
into this repository: | ||
|
||
* `scripts/opentitan/tests-passing.txt` | ||
* `scripts/opentitan/tests-flaky.txt` | ||
|
||
All tests in `tests-passing.txt` are expected to pass. Failures indicate a | ||
regression in either QEMU or Earlgrey. The script will fail if there is a | ||
mismatch between the tests that we expect to pass and the actual results. | ||
|
||
Some tests may be flaky and pass or fail on different runs of the same QEMU | ||
and OpenTitan checkouts. These tests can be added to the `tests-flaky.txt` list | ||
to cause the script to ignore them. |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,5 +1,15 @@ | ||
//sw/device/silicon_creator/lib/ownership:owner_verify_functest_sim_qemu_rom_with_fake_keys | ||
//sw/device/silicon_creator/lib/sigverify:mod_exp_ibex_functest_hardcoded_sim_qemu_rom_with_fake_keys | ||
//sw/device/silicon_creator/lib/sigverify/sphincsplus/test:verify_test_kat1_sim_qemu_rom_with_fake_keys | ||
//sw/device/silicon_creator/lib/sigverify/sphincsplus/test:verify_test_kat2_sim_qemu_rom_with_fake_keys | ||
//sw/device/silicon_creator/lib/sigverify/sphincsplus/test:verify_test_kat3_sim_qemu_rom_with_fake_keys | ||
//sw/device/silicon_creator/lib/sigverify/sphincsplus/test:verify_test_kat4_sim_qemu_rom_with_fake_keys | ||
//sw/device/silicon_creator/lib/sigverify/sphincsplus/test:verify_test_kat5_sim_qemu_rom_with_fake_keys | ||
//sw/device/silicon_creator/lib/sigverify/sphincsplus/test:verify_test_kat6_sim_qemu_rom_with_fake_keys | ||
//sw/device/silicon_creator/lib/sigverify/sphincsplus/test:verify_test_kat7_sim_qemu_rom_with_fake_keys | ||
//sw/device/silicon_creator/lib/sigverify/sphincsplus/test:verify_test_kat9_sim_qemu_rom_with_fake_keys | ||
Comment on lines
+3
to
+10
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I find these failures surprising since I've never seen them fail personally. I think it's fine to add for now though if you've seen this, and we can remove them again later if needed. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. For me it fails more often than not:
It must be timing related There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Ah, I think it might be timing related - but not in the way you think. Running that test myself locally:
I think it heavily depends upon the speed of the host machine. This could explain why you keep seeing errors on the CI runner (and locally) but I don't? What is the failure mode - is it just a genuine timeout? If so, these tests probably need tagging with longer timeouts in OpenTitan. |
||
//sw/device/tests/autogen:alert_test_sim_qemu_rom_with_fake_keys | ||
//sw/device/tests/crypto:aes_gcm_timing_test_sim_qemu_rom_with_fake_keys | ||
//sw/device/tests/crypto:rsa_2048_keygen_functest_sim_qemu_rom_with_fake_keys | ||
//sw/device/tests:edn_auto_mode_sim_qemu_rom_with_fake_keys | ||
//sw/device/tests:rv_core_ibex_rnd_test_sim_qemu_rom_with_fake_keys |
Uh oh!
There was an error while loading. Please reload this page.