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

[Hans-Peter Nilsson]

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=46f238477f5e83cba9dc79d1e14c0f6acbeda37b

commit 46f238477f5e83cba9dc79d1e14c0f6acbeda37b
Author: Hans-Peter Nilsson <hp@axis.com>
Date:   Mon Feb 14 23:50:42 2022 +0100

    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.

Diff:
---
 sim/testsuite/cris/hw/rv-n-cris/irq1.ms | 1 +
 1 file changed, 1 insertion(+)

diff --git a/sim/testsuite/cris/hw/rv-n-cris/irq1.ms b/sim/testsuite/cris/hw/rv-n-cris/irq1.ms
index f3e6f2e7bee..a7c82dc5566 100644
--- a/sim/testsuite/cris/hw/rv-n-cris/irq1.ms
+++ b/sim/testsuite/cris/hw/rv-n-cris/irq1.ms
@@ -1,3 +1,4 @@
+#progos: nowhere:disabled-due-to-randomness
 #mach: crisv10 crisv32
 #sim(crisv10): --hw-device "/rv/trace? true"
 #sim(crisv32): --hw-device "/rv/trace? true"