ci: Bump msan to llvm-18 #29676

1. 
   maflcko commented at 9:39 am on March 19, 2024: member

   Last one: https://github.com/bitcoin/bitcoin/pull/28476
2. 
   DrahtBot commented at 9:39 am on March 19, 2024: contributor

   The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.

   Code Coverage

   For detailed information about the code coverage, see the test coverage report.

   Reviews

   See the guideline for information on the review process.

   Type	Reviewers
   ACK	fanquake

   If your review is incorrectly listed, please react with 👎 to this comment and the bot will ignore it on the next update.

3. DrahtBot added the label Tests on Mar 19, 2024
4. 
   fanquake commented at 10:14 am on March 19, 2024: member

   Is there a workaround for https://github.com/llvm/llvm-project/issues/79620 ? I had branch to do the same bump, but it was blocked on at least this issue. We will also need to account for this, depending on the kernel version: https://github.com/llvm/llvm-project/issues/78354.
5. DrahtBot added the label CI failed on Mar 19, 2024
6. 
   DrahtBot commented at 12:46 pm on March 19, 2024: contributor

   🚧 At least one of the CI tasks failed. Make sure to run all tests locally, according to the documentation.

   Possibly this is due to a silent merge conflict (the changes in this pull request being incompatible with the current code in the target branch). If so, make sure to rebase on the latest commit of the target branch.

   Leave a comment here, if you need help tracking down a confusing failure.

   Debug: https://github.com/bitcoin/bitcoin/runs/22825353269

7. maflcko force-pushed on Mar 19, 2024
8. ci: Bump msan to llvm-18 faecf3a7e6
9. maflcko force-pushed on Mar 19, 2024
10. 
    maflcko commented at 5:05 pm on March 19, 2024: member

    Looks like this also fixes the outstanding msan fuzz CI issue?
11. 
    fanquake commented at 5:44 pm on March 19, 2024: member

    Appears to be the case. MSAN fuzz is running for me on x86_64
12. DrahtBot removed the label CI failed on Mar 19, 2024
13. fanquake approved
14. 
    fanquake commented at 11:56 am on March 20, 2024: member

    ACK faecf3a7e6779c2cacadd91a6eba446431778849 - There is now a 18.1.2, but given it doesn’t fix the instrumenting in libunwind, we don’t need that here. I’ve tested that both jobs are now working on both arches.
15. fanquake merged this on Mar 20, 2024
16. fanquake closed this on Mar 20, 2024

    ---

17. maflcko deleted the branch on Mar 20, 2024
18. 
    fanquake commented at 12:03 pm on March 20, 2024: member

    Also kicked https://cirrus-ci.com/task/6539451837448192 in qa-assets for a look.
19. fanquake referenced this in commit f824d65de2 on Mar 21, 2024
20. fanquake referenced this in commit a7116c8feb on Mar 21, 2024
21. fanquake referenced this in commit b3cd952495 on Mar 26, 2024
22. bitcoin locked this on Mar 20, 2025

Contributors
maflcko DrahtBot fanquake

Labels
Tests