Backports:
[30.x] Backports #35083
pull fanquake wants to merge 4 commits into bitcoin:30.x from fanquake:even_more_30_x_backports changing 7 files +30 −28-
fanquake commented at 2:34 PM on April 15, 2026: member
-
561d072e05
test: Add missing self.options.timeout_factor scale in tool_bitcoin_chainstate.py
Apply the timeout factor inside the add_block function. Also, force named args for the two expected strings. Also, add trailing comma for style. Github-Pull: #35080 Rebased-From: fa02eb87df0b4a615a3e027711326f5506e5507a
- DrahtBot added the label Backport on Apr 15, 2026
-
DrahtBot commented at 2:35 PM on April 15, 2026: contributor
<!--e57a25ab6845829454e8d69fc972939a-->
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.
<!--006a51241073e994b41acfe9ec718e94-->
Code Coverage & Benchmarks
For details see: https://corecheck.dev/bitcoin/bitcoin/pulls/35083.
<!--021abf342d371248e50ceaed478a90ca-->
Reviews
See the guideline for information on the review process.
Type Reviewers ACK achow101 If your review is incorrectly listed, please copy-paste <code><!--meta-tag:bot-skip--></code> into the comment that the bot should ignore.
<!--5faf32d7da4f0f540f40219e4f7537a3-->
- fanquake added this to the milestone 30.3 on Apr 15, 2026
- fanquake force-pushed on Apr 30, 2026
- fanquake marked this as ready for review on Apr 30, 2026
-
willcl-ark commented at 1:47 PM on April 30, 2026: member
If #34855#pullrequestreview-4205518227 applies to 29.x, then I think it applies here too:
-
9632450ff6
multi_index: fix compilation failure with boost >= 1.91
This effectively reverts a3cb309e7c31853f272bffaa65fb6ab0a7cc4083 from PR #30194. That PR reduced the multi_index type signatures as recommended upstream, but this is no longer supported as of boost 1.91 because it is no longer necessary. 1.91 drops support for the pre-c++11 work-arounds that bloated the type signatures to begin with. The upstream `BOOST_MULTI_INDEX_ENABLE_MPL_SUPPORT` define is meant to provide compatibility with removed features, but it does not work for this case. Using `indexed_by` directly when defining the `multi_index` (as opposed to inheriting from it) works with all versions, and avoids the use of the back-compat define. This is a slight regression when building against boost < 1.91 because the bloated type signatures are reintroduced in that case, but it's not significant enough to go to the trouble of introducing version detection and ifdefs. Github-Pull: #35175 Rebased-From: 0bc9d354dfd8074d1c36a891a69b6585a8775c65
- fanquake force-pushed on May 1, 2026
-
33d66c67ee
ci: unconfine seccomp for i686 no IPC
Docker 29.4.2 blocks `socketcall(2)` in the default seccomp profile: https://docs.docker.com/engine/release-notes/29/#2942 https://github.com/moby/profiles/releases/tag/seccomp%2Fv0.2.2 https://github.com/moby/moby/pull/52501 That affects the `i686, no IPC` job because it runs 32-bit Linux test binaries inside Docker. Add Docker's documented `--security-opt seccomp=unconfined` workaround to this job's `CI_CONTAINER_CAP` - the hook `ci/test/02_run_container.py` already appends to `docker run`. This restores socket availability for the 32-bit test binaries throughout the job: https://docs.docker.com/engine/security/seccomp/#run-without-the-default-seccomp-profile Github-Pull: #35202 Rebased-From: 11c9ef92a8daf030f75f88f324396b2248c65a64
-
doc: update release notes for v30.x 6c3f40117f
- fanquake force-pushed on May 5, 2026
-
achow101 commented at 8:20 AM on May 6, 2026: member
ACK 6c3f40117fc212b0fe60a3519cce2e0218179921
- achow101 merged this on May 6, 2026
- achow101 closed this on May 6, 2026
- fanquake deleted the branch on May 6, 2026