libFuzzer fuzzer-leak.test and fuzzer-finalstats.test are unstable #97712
Labels
Comments
DavidSpickett
added a commit
that referenced
this issue
Jul 4, 2024
This has been flaky and reporting a lot of unrelated failures to PRs. See #97712
|
(apologies for the blunt approach here just disabling it completely, I'm not very familiar with the internal workings of the fuzzer) |
|
#97396 (comment) Some more examples, in case any pattern emerges when looking at the build times/worker names/etc. |
kbluck
pushed a commit
to kbluck/llvm-project
that referenced
this issue
Jul 6, 2024
This has been flaky and reporting a lot of unrelated failures to PRs. See llvm#97712
DavidSpickett
added a commit
that referenced
this issue
Jul 9, 2024
This test is flaky and has been reporting irrelevant failures to PRs on Github for example: #97829 (comment) https://lab.llvm.org/buildbot/#/builders/66/builds/1159 Adding this to #97712.
DavidSpickett
changed the title
|
Also temporarily disabled |
|
finalstats potentially fixed by #96914 |
aaryanshukla
pushed a commit
to aaryanshukla/llvm-project
that referenced
this issue
Jul 14, 2024
This test is flaky and has been reporting irrelevant failures to PRs on Github for example: llvm#97829 (comment) https://lab.llvm.org/buildbot/#/builders/66/builds/1159 Adding this to llvm#97712.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
compiler-rt/test/fuzzer/fuzzer-leak.testhas been the cause of a lot of unrelated failures since buildbot started posting statues to PRs.For example: #97397 (comment)
I know in general this test can be sensitive to the resources available on the machine at the time, but perhaps something can be done to make it deterministic?
The text was updated successfully, but these errors were encountered: