bitcoin: intermittent issue in rpc_signer.py (enumeratesigners timeout) under GLIBCXX debug mode
https://cirrus-ci.com/task/5094568045051904?logs=ci#L4419
[18:26:32.573] test_framework.authproxy.JSONRPCException: 'enumeratesigners' RPC took longer than 1200.000000 seconds. Consider using larger timeout for calls that take longer to return. (-344)
Looking at the full log, the test is just idle and then times out. However, there is no indication why the RPC does not proceed.
About this issue
- Original URL
- State: open
- Created 2 years ago
- Comments: 26 (25 by maintainers)
Commits related to this issue
- Merge bitcoin/bitcoin#32560: ci: Move DEBUG=1 to centos task fa58d6cdab000df288501db4a71487804b08ba4b ci: Move DEBUG=1 to centos task (MarcoFalke) Pull request description: The glibcxx debug mode... — committed to bitcoin/bitcoin by fanquake 2 years ago
- ci: Downgrade DEBUG=1 to -D_GLIBCXX_ASSERTIONS in centos task to work around https://github.com/bitcoin/bitcoin/issues/32524#issuecomment-2900903169 — committed to maflcko/bitcoin-core by deleted user a year ago
- ci: Downgrade DEBUG=1 to -D_GLIBCXX_ASSERTIONS in centos task to work around https://github.com/bitcoin/bitcoin/issues/32524#issuecomment-2900903169 — committed to maflcko/bitcoin-core by deleted user a year ago
- Merge bitcoin/bitcoin#32586: ci: Downgrade DEBUG=1 to -D_GLIBCXX_ASSERTIONS in centos task fa079538e32d20aec6786c93e1117da1e8ea0cab ci: Downgrade DEBUG=1 to -D_GLIBCXX_ASSERTIONS in centos task (Marc... — committed to bitcoin/bitcoin by fanquake a year ago
I’ve created 50 runs and they all passed: https://cirrus-ci.com/task/5325312260571136 So I guess this is related. I’ll try to get the gdb bt next.
The debug mode keeps state in additional structs/fields, so my bet would be that one of the states is multi-thread unsafe, but that is just a wild guess.
Sure. If this is unlikely to cause issues for real users, that makes more sense, the point of the CI is not to keep us patching the code to make the CI happy 😄
So far it looks like this can only happen with gcc-13 (or older) and GLIBCXX debug mode. I don’t think any real user is running in production with the std lib debug mode, so an alternative would be to just fixup the CI?
For reference, the end-user setting
-D_GLIBCXX_ASSERTIONSpassed 25 times: https://cirrus-ci.com/task/5739615073599488Backtrace with file names and lines:
Same https://cirrus-ci.com/task/4561849141690368?logs=ci#L6059
So I guess this was recently introduced