The WalletMigration benchmark is currently failing on CI.
This PR temporarily disables it until the issue is resolved.
An alternative to #32302.
<!--e57a25ab6845829454e8d69fc972939a-->
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.
<!--006a51241073e994b41acfe9ec718e94-->
For details see: https://corecheck.dev/bitcoin/bitcoin/pulls/32306.
<!--021abf342d371248e50ceaed478a90ca-->
See the guideline for information on the review process.
| Type | Reviewers |
|---|---|
| ACK | TheCharlatan, maflcko |
If your review is incorrectly listed, please react with 👎 to this comment and the bot will ignore it on the next update.
<!--174a7506f384e20aa4161008e828411d-->
Reviewers, this pull request conflicts with the following ones:
implicit-integer-sign-change check for serialize.h by l0rinc)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.
357 | @@ -358,7 +358,8 @@ jobs: 358 | ./src/univalue/unitester.exe 359 | 360 | - name: Run benchmarks 361 | - run: ./bin/bench_bitcoin.exe -sanity-check 362 | + # TODO: Fix the `WalletMigration` benchmark and re-enable it. 363 | + run: ./bin/bench_bitcoin.exe -sanity-check -filter='^(?!WalletMigration$).+$'
Yet another alternative would be to comment out BENCHMARK(WalletMigration, benchmark::PriorityLevel::LOW); instead (so that when we fix it, we won't need to touch ci workflows again)
Will it have a broader impact beyond the CI?
I've pushed #32309 which seems to fix the build (based on https://github.com/l0rinc/bitcoin/pull/9)
ACK 18a035145d6abb41e49711de60c4feabe3ba31e9
Hope this gets fixed properly soon though.
lgtm ACK 18a035145d6abb41e49711de60c4feabe3ba31e9
Makes sense to temporarily disable a single known-to-fail benchmark, until it is known to work.