Both newly added tests fail in Release.
This reverts commit 52aa4e210744361a5ed6dc50fef78ed91706e508.
Differential D93957
Revert "[ThinLTO][test] Add visibility related tests" bgraur on Dec 31 2020, 3:36 AM. Authored by
Details Both newly added tests fail in Release. This reverts commit 52aa4e210744361a5ed6dc50fef78ed91706e508.
Diff Detail
Event TimelineComment Actions This was due to a -DLLVM_ENABLE_ASSERTIONS=off vs -DLLVM_ENABLE_ASSERTIONS=on difference. llvm-lto2 needs -enable-import-metadata Comment Actions Ideally, this roll-forward should also have included this fix. Comment Actions I have checked some Linux/macOS/Windows built bots and even tested on a ppc64le machine. The description of this commit isn't clear about what happened. Comment Actions The descritption is: "Both newly added tests fail in Release." That means: Checking any build bots won't show any failure because the problem is a test failure, not a build breakage. Comment Actions Most build bots are configured with -DLLVM_ENABLE_ASSERTIONS=ON. Anyhow I figured out the root cause and make the behavior not dependent on -DLLVM_ENABLE_ASSERTIONS= to prevent future issues like this. Comment Actions
Are you suggesting that buildbots don't actually run tests? Comment Actions Not sure how the build bots are configured. What is sure is that if you run the tests using the llvm tools these tests will always fail in Release. So, the conclusion is one of the following: |