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
ci: remove --with-asm=no (secp256k1) from MSAN jobs #29742
Conversation
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers. Code CoverageFor detailed information about the code coverage, see the test coverage report. ReviewsSee the guideline for information on the review process.
If your review is incorrectly listed, please react with 👎 to this comment and the bot will ignore it on the next update. ConflictsReviewers, this pull request conflicts with the following ones:
If you consider this pull request important, please also help to review the conflicting pull requests. Ideally, start with the one that should be merged first. |
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.
Nice. Obvious concept ACK. Can discuss the secp subtree bump separately.
Why is the llvm 18.1.2 bump bundled here, though?
Mostly just because I was going to include another MSAN patch, to fix the instrumentation on libuwind (llvm/llvm-project#84348) but haven't quite got that working yet. Note that depending on timings, if llvm/llvm-project#86201 goes into the next 18.x release, I'll want to bump/pull that in too, because it'll remove the need for a workaround when running the CI locally on newer kernels (same issue as this one bitcoin-core/secp256k1#1506). Happy to split up the changes in any case, just had a MSAN bundle to test here. |
🚧 At least one of the CI tasks failed. Make sure to run all tests locally, according to the Possibly this is due to a silent merge conflict (the changes in this pull request being Leave a comment here, if you need help tracking down a confusing failure. |
Seems to be failing in CI. I guess due to build-architecture differences, or is there a bug in the CI system? |
I think so: x86_64 |
d2f8429
to
c2f32a0
Compare
Ready for bump now that bitcoin-core/secp256k1#1512 is merged. |
c2f32a0
to
13a5975
Compare
Converted to a proper subtree bump. |
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.
Concept ACK on removing --with-asm=no
53eec53 Squashed 'src/secp256k1/' changes from efe85c70a2..d8311688bd (fanquake) Pull request description: Updates the libsecp256k1 subtree to bitcoin-core/secp256k1@d831168. Part of #29742. See that PR for more details, the particularly relevant changes are: * bitcoin-core/secp256k1#1496 * bitcoin-core/secp256k1#1512 ACKs for top commit: theuni: ACK 4654cc3 jonasnick: utACK 4654cc3 Tree-SHA512: 84e711e9245ced6cc679e082f597d096361d8824c6ff7de2d4d7f59adb3316464b3643ffa588a899345cb88532672a66968b6c66c51b1924adf4441f54427277
Can be dropped after bitcoin/bitcoin#29803. Equivalent in our CI is bitcoin/bitcoin#29742.
13a5975
to
61641e2
Compare
Opened google/oss-fuzz#11785 for oss-fuzz. Also cc @jonasnick. |
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.
ACK 61641e2.
Have run this successfully on all 4 MSAN jobs locally. |
lgtm ACK 61641e2 |
Can be dropped after bitcoin/bitcoin#29803. Equivalent in our CI is bitcoin/bitcoin#29742.
Bumps LLVM to
18.1.3
:Drops
--with-asm=no
(only being passed to secp256k1) from the MSAN CI. New MSAN annotations were pulled in as part of #29803.