-
Notifications
You must be signed in to change notification settings - Fork 125
[BOLT] Increase nfc-test coverage #467
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BOLT] Increase nfc-test coverage #467
Conversation
|
This PR triggers in-tree tests for additional source changes. Running out-of-tree tests is not needed. The main motivation is to cover patches Once merged, any changes to I've verified these internally and got expected behaviour in the below patches:
|
b03cc23 to
9ffb74e
Compare
8f4aaf1 to
326abf3
Compare
|
Forced pushed to rebase. Also now would run the tests unconditionally, if for any reason the nfc-check-setup.py had failed. |
aaupov
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks
9ffb74e to
154a315
Compare
68cc918 to
a16e2be
Compare
154a315 to
ff25d5c
Compare
a16e2be to
74469fb
Compare
Use `--check-bolt-sources` from nfc-check-setup.py to run tests when source files change between the current and previous revisions. This triggers only in-tree tests. When the llvm-bolt binary changes, both in-tree and out-of-tree tests are run.
If the NFC check setup fails to execute for any reason, we still want to run tests unconditionally. To implement this, we now use skip markers: tests run when these markers are not present. If the current and previous llvm-bolt binaries are identical, we create two skip markers for in-tree and out-of-tree tests. If there are other BOLT source changes, we delete the in-tree skip marker so those test Can proceed.
74469fb to
cdc34f7
Compare
Use
--check-bolt-sourcesfrom nfc-check-setup.py to run tests when sourcefiles change between the current and previous revisions.
Skip markers are used to indicate which tests should run: when not present the
tests run. Examples:
skip markers for in-tree and out-of-tree tests.
those test can proceed.