diff options
author | Orlando Cazalet-Hyams <orlando.hyams@sony.com> | 2024-03-15 15:49:39 +0000 |
---|---|---|
committer | GitHub <noreply@github.com> | 2024-03-15 15:49:39 +0000 |
commit | 7337db72ed334f8389601f160b762e50c4e61c25 (patch) | |
tree | c100f19b37029f7e9154b5a3a15280fb267c63cb /llvm/unittests/Support/VirtualFileSystemTest.cpp | |
parent | a4ca07f13b560b4f6fa5459eef7159e4f9ee9a6b (diff) | |
download | llvm-7337db72ed334f8389601f160b762e50c4e61c25.zip llvm-7337db72ed334f8389601f160b762e50c4e61c25.tar.gz llvm-7337db72ed334f8389601f160b762e50c4e61c25.tar.bz2 |
Add ALLOW_RETRIES to flaky test dbg-record-roundtrip.ll (#85410)
Something strange is happening in this test.
If the llvm-as output is piped into llvm-link in the final RUN lines
then this test fails on my machine (1 in 200) using WSL2. If the
verify-uselistorder RUN lines are removed then it doesn't fail on my
machine (in 10,000+). If the llvm-as and llvm-link RUN lines mentioned
at the start are removed then it doesn't fail on my machine (in
10,000+).
Writing the llvm-as output to a temporary file for llvm-link to read on
those final RUN lines, the test doesn't fail on my machine (in 10,000+).
But it _does_ fail on a bot:
https://lab.llvm.org/buildbot/#/builders/245/builds/21930. So clearly my
workaround doesn't solve the underlying problem (and I have no idea what
that is).
Diffstat (limited to 'llvm/unittests/Support/VirtualFileSystemTest.cpp')
0 files changed, 0 insertions, 0 deletions