ci: Bump centos gcc to 12 #31477

1. 
   maflcko commented at 8:32 am on December 12, 2024: member

   Currently the centos stream9 CI task is using gcc-11. This is fine, because this is also the minimum supported.

   However:

   • There is already a CI task that is checking the minimum supported version: https://github.com/bitcoin/bitcoin/blob/62bd61de110b057cbfd6e31e4d0b727d93119c72/ci/test/00_setup_env_native_previous_releases.sh#L11-L12
   • The CI log is a bit useless, because it is mostly just #warning _FORTIFY_SOURCE > 2 is treated like 2 on this platform [-Werror=cpp]. This makes it harder to spot real warnings, such as #31476

   Fix both issues by using gcc-12.

2. 
   DrahtBot commented at 8:32 am on December 12, 2024: contributor

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

   Code Coverage & Benchmarks

   For details see: https://corecheck.dev/bitcoin/bitcoin/pulls/31477.

   Reviews

   See the guideline for information on the review process.

   Type	Reviewers
   ACK	hebasto

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

   Conflicts

   Reviewers, this pull request conflicts with the following ones:

   • #31349 (ci: detect outbound internet traffic generated while running tests by vasild)
   • #30997 (build: Switch to Qt 6 by hebasto)

   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.

3. DrahtBot added the label Tests on Dec 12, 2024
4. ci: Bump centos gcc fa47baa03b
5. maflcko force-pushed on Dec 12, 2024
6. DrahtBot added the label CI failed on Dec 12, 2024
7. 
   DrahtBot commented at 8:53 am on December 12, 2024: contributor

   🚧 At least one of the CI tasks failed. Debug: https://github.com/bitcoin/bitcoin/runs/34303618224

   Try to run the tests locally, according to the documentation. However, a CI failure may still happen due to a number of reasons, for example:

   • Possibly 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.

   • A sanitizer issue, which can only be found by compiling with the sanitizer and running the affected test.

   • An intermittent issue.

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

8. DrahtBot removed the label CI failed on Dec 12, 2024
9. hebasto approved
10. 
    hebasto commented at 11:36 am on December 12, 2024: member

    ACK fa47baa03bcfcf44fb2ed05f009a32d32f860c45.
11. fanquake merged this on Dec 13, 2024
12. fanquake closed this on Dec 13, 2024

    ---

13. maflcko deleted the branch on Dec 13, 2024
14. sedited referenced this in commit 230a439a4a on Jan 17, 2025
15. stickies-v referenced this in commit d760fd3dda on Mar 17, 2025
16. stickies-v referenced this in commit cc83553352 on Mar 17, 2025
17. stickies-v referenced this in commit 2614933f06 on Mar 17, 2025
18. stickies-v referenced this in commit b70418c5fc on Mar 17, 2025
19. stickies-v referenced this in commit 69f8a1fe50 on Mar 17, 2025
20. bug-castercv502 referenced this in commit 44b075fe71 on Sep 28, 2025
21. bitcoin locked this on Dec 13, 2025

Contributors
maflcko DrahtBot hebasto

Labels
Tests