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

Update rvfi_tracer and cva6.py #2684

Open
wants to merge 5 commits into
base: master
Choose a base branch
from

Conversation

AyoubJalali
Copy link
Contributor

This MR update rvfi_tracer to help the team debug, also I add the capability of randomizing the sv_seed by default

Copy link
Contributor

github-actions bot commented Jan 3, 2025

❌ failed run, report available here.

@@ -775,7 +775,7 @@ def parse_args(cwd):
help="switch AXI agent mode: yes for Active, no for Passive")
parser.add_argument("--gen_sv_seed", type=int, default=0,
help="Run test N times with random seed")
parser.add_argument("--sv_seed", type=str, default="1",
parser.add_argument("--sv_seed", type=str, default=str(random.getrandbits(31)),
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If the seed is random, the CI tests will be executed with different seeds. This means the CI will not be deterministic. This can be a problem when executing Dhrystone or Coremark tests for instance for which we monitor cycle number.
Moreover some CI tests can have random behavior in relation to the seed. Debug can be more difficult.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You can fix you're sv_seed using cva6.py option --sv_seed = n , by default sv_seed is always 1 and this limit finding bugs and use 100% of the UVM advantage (randomization), for now in CI all tests are running with only one sv_seed.

But we should store uvm seed in a specific file and store them in the artifacts

Copy link
Contributor

github-actions bot commented Jan 6, 2025

❌ failed run, report available here.

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

Successfully merging this pull request may close these issues.

2 participants