[compiler-rt] d685508 - [libFuzzer] Change sig-trap test to allow expected output strings in any order (#157407)

[via llvm-commits]

Author: Dan Blackwell
Date: 2025-09-10T08:25:12+01:00
New Revision: d685508bec02a676383b284d268fe8a2e4cbf7f3

URL: https://github.com/llvm/llvm-project/commit/d685508bec02a676383b284d268fe8a2e4cbf7f3
DIFF: https://github.com/llvm/llvm-project/commit/d685508bec02a676383b284d268fe8a2e4cbf7f3.diff

LOG: [libFuzzer] Change sig-trap test to allow expected output strings in any order (#157407)

I have seen some flakiness in this test where the 2 checked strings
appear in a different order. Due to buffering of writes, and that one of
these strings is written during the signal handler, I think this is
valid. 

This PR relaxes the test to allow those strings to appear in
either order.

Added: 
    

Modified: 
    compiler-rt/test/fuzzer/sig-trap.test

Removed: 
    


################################################################################
diff  --git a/compiler-rt/test/fuzzer/sig-trap.test b/compiler-rt/test/fuzzer/sig-trap.test
index 30d9d47f4d81f..60208c486a87a 100644
--- a/compiler-rt/test/fuzzer/sig-trap.test
+++ b/compiler-rt/test/fuzzer/sig-trap.test
@@ -5,7 +5,7 @@ UNSUPPORTED: target={{.*windows.*}}
 RUN: %cpp_compiler %S/SigTrapTest.cpp -o %t
 
 RUN: not %run %t            2>&1 | FileCheck %s
-CHECK: BINGO
-CHECK: ERROR: libFuzzer: deadly signal
+CHECK-DAG: BINGO
+CHECK-DAG: ERROR: libFuzzer: deadly signal
 
 RUN: trap "%run %t -handle_trap=0" TRAP