Note the first cherry-pick is not clean, because due to Google tooling issues, it accidently contained a revert of the prior two commits. See https://github.com/google/leveldb/pull/1249 for more details.
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.
</details>
DrahtBot added the label CI failed on Jan 30, 2025
victorvianna
commented at 5:48 PM on January 30, 2025:
none
FYI the upstream PR landed
fanquake force-pushed on Mar 7, 2025
fanquake renamed this: [WIP] leveldb: pull upstream C++23 changes leveldb: pull upstream C++23 changes on Mar 7, 2025
fanquake
commented at 5:10 PM on March 7, 2025:
member
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-08-05 07:51 UTC
This site is hosted by @0xB10C More mirrored repositories can be found on mirror.b10c.me