[all-commits] [llvm/llvm-project] 7337db: Add ALLOW_RETRIES to flaky test dbg-record-roundtr...

[Orlando Cazalet-Hyams via All-commits]

  Branch: refs/heads/main
  Home:   https://github.com/llvm/llvm-project
  Commit: 7337db72ed334f8389601f160b762e50c4e61c25
      https://github.com/llvm/llvm-project/commit/7337db72ed334f8389601f160b762e50c4e61c25
  Author: Orlando Cazalet-Hyams <orlando.hyams at sony.com>
  Date:   2024-03-15 (Fri, 15 Mar 2024)

  Changed paths:
    M llvm/test/Bitcode/dbg-record-roundtrip.ll

  Log Message:
  -----------
  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).



To unsubscribe from these emails, change your notification settings at https://github.com/llvm/llvm-project/settings/notifications