sim/testsuite/cris/hw/rv-n-cris/irq1.ms: Disable due to randomness

For reasons that remain largely to be investigated (besides
the apparent lack of synchronization between two processes),
this test fails randomly, with two different sets of common
outputs.  Curiously, that doesn't happen for the other
similar tests.  There's a comment that mentions this, though
that doesn't make it a sustainable part of a test-suite.
(Known-blinking tests should be disabled until fixed.)

sim/testsuite/cris:
	* hw/rv-n-cris/irq1.ms: Disable by use of a never-matched
	"progos" value.
This commit is contained in:
Hans-Peter Nilsson
2022-02-14 23:50:42 +01:00
committed by Hans-Peter Nilsson
parent 56ba3848dc
commit 46f238477f

View File

@ -1,3 +1,4 @@
#progos: nowhere:disabled-due-to-randomness
#mach: crisv10 crisv32 #mach: crisv10 crisv32
#sim(crisv10): --hw-device "/rv/trace? true" #sim(crisv10): --hw-device "/rv/trace? true"
#sim(crisv32): --hw-device "/rv/trace? true" #sim(crisv32): --hw-device "/rv/trace? true"