Fix coverage files generation #7401
Draft
Conversation
This file contains 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
RenjiSann
force-pushed
the
coverage
branch
2 times, most recently
from
09a916d to
9020634
Compare
|
GNU testsuite comparison: |
|
having at least linux passing would be an improvement! :) |
RenjiSann
force-pushed
the
coverage
branch
2 times, most recently
from
ab91264 to
4f801c9
Compare
|
GNU testsuite comparison: |
|
GNU testsuite comparison: |
RenjiSann
force-pushed
the
coverage
branch
3 times, most recently
from
66fd2fa to
5812e9c
Compare
|
GNU testsuite comparison: |
RenjiSann
force-pushed
the
coverage
branch
8 times, most recently
from
cc00e9b to
51e845c
Compare
|
FINALLY it seems to work. However, there is still a problem with result upload on codecov |
|
GNU testsuite comparison: |
RenjiSann
force-pushed
the
coverage
branch
2 times, most recently
from
4178c97 to
1545a9b
Compare
|
GNU testsuite comparison: |
|
GNU testsuite comparison: |
This reverts commit ca92bff.
|
GNU testsuite comparison: |
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.
Fixes #7282 issue about LLVM instrumentation.
The remain BIG issue is that the quantity of trace files generated by the WHOLE testsuite is absolutely massive, because 1 call to the tested binary produces 1 trace file that is around 5 MiB.
On my machine, the testsuite had to stop at ~80% completion because it had filled my disk with 92GiB of
.profrawfiles.