You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Debugging a test makefile cleanup, I realized why t_prot_lib and t_noprot_lib seem to fail occasionally for me, but then passes on rerun.
Both run t_prot_lib_secret.pl, so there's up to three running (t_prot_lib's, noprot's and secret form the original driver). If they run simultaneously they break.
Suggest we leave t_prot_lib_secret.pl as is, but have t_prot_lib/t_noprot_lib instead of calling the secret.pl test, just run the verilator command standalone putting output in e.g. {obj_dir}/secret/.... (or otherwise). Then each test will be self-contained.
Let me know if you prefer if I do this.
The text was updated successfully, but these errors were encountered:
I'm not sure why you would have seen this with t_noprot_lib as it does not call t_prot_lib_secret.pl (since it's building a monolithic version of the same thing). I looked around in Travis for an example of any of these reruns but couldn't find any. However, that may be a result of Travis' limited core count.
Author Name: Wilson Snyder (@wsnyder)
Original Redmine Issue: 1580 from https://www.veripool.org
Original Assignee: Todd Strader (@toddstrader)
Debugging a test makefile cleanup, I realized why t_prot_lib and t_noprot_lib seem to fail occasionally for me, but then passes on rerun.
Both run t_prot_lib_secret.pl, so there's up to three running (t_prot_lib's, noprot's and secret form the original driver). If they run simultaneously they break.
Suggest we leave t_prot_lib_secret.pl as is, but have t_prot_lib/t_noprot_lib instead of calling the secret.pl test, just run the verilator command standalone putting output in e.g. {obj_dir}/secret/.... (or otherwise). Then each test will be self-contained.
Let me know if you prefer if I do this.
The text was updated successfully, but these errors were encountered: