Compiler ICEs in CI? #36125

issue DrahtBot opened this issue on August 31, 2026
  1. DrahtBot commented at 8:51 AM on August 31, 2026: contributor

    Looks like there are a bunch of GCC 12 ICEs in the Warp CI:

    Not sure why they would pop up now, when they never happened before?

  2. DrahtBot added the label CI failed on Aug 31, 2026
  3. maflcko added the label Brainstorming on Aug 31, 2026
  4. maflcko commented at 8:55 AM on August 31, 2026: member

    cc @willcl-ark Maybe someone can ask warpbuild if the two builds ran on the same hardware/VM. If yes, maybe that hardware should be checked for defects?

  5. willcl-ark commented at 12:54 PM on September 1, 2026: member

    Done 👍🏼

  6. maflcko commented at 1:02 PM on September 1, 2026: member

    Thx.

    On the other hand, both happening for the exact same CI config (and on no other config), seems to indicate that maybe something may be wrong in that config (or any of it's dependencies)?

    An OOM seems unlikely, given the 20GiB of free RAM.

    Maybe this will fix itself, when minimum GCC is switched to 13.

  7. DrahtBot commented at 1:09 PM on September 1, 2026: contributor

    Ok, nvm. Clang 17 also ICEs:

  8. DrahtBot renamed this:
    GCC 12 ICE in CI?
    Compiler ICEs in CI?
    on Sep 1, 2026
  9. willcl-ark commented at 3:41 PM on September 1, 2026: member

    Warp confirmed the two first jobs were on different hardware too.

  10. maflcko commented at 5:18 PM on September 1, 2026: member

    Not sure what the issue is, but this is getting out of hand:


github-metadata-mirror

This is a metadata mirror of the GitHub repository bitcoin/bitcoin. This site is not affiliated with GitHub. Content is generated from a GitHub metadata backup.
generated: 2026-09-09 07:56 UTC