[BOLT][test] Update perf2bolt/perf_test.test #73482
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
perf_test keeps failing on bolt-aarch64-ubuntu-clang-shared: https://lab.llvm.org/buildbot/#/builders/221/builds/20330 The reason is likely that there are no samples due to short test runtime. Bump up the running time 10x and remove unneeded headers. With the change that test passed on a buildbot host 10/10 times.
|
LGTM, Maybe, adding "-F max" to "perf record" can also address the issue? I am not sure which one is better :) |
I checked that first but it didn't help. |
Oh, okay, it looks like the current modification is the best. |
|
@llongint can you please approve then? |
llongint
approved these changes
Nov 28, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
perf_test keeps failing on bolt-aarch64-ubuntu-clang-shared:
https://lab.llvm.org/buildbot/#/builders/221/builds/20330
The reason is likely that there are no samples due to short test runtime.
Bump up the running time 10x and remove unneeded headers.
With the change that test passed on a buildbot host 10/10 times.