-
Notifications
You must be signed in to change notification settings - Fork 35.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
test: increase rpc_timeout for fundrawtx test_transaction_too_large #21410
test: increase rpc_timeout for fundrawtx test_transaction_too_large #21410
Conversation
This patch is green on https://bitcoinbuilds.org/?build=8266 |
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers. ConflictsReviewers, this pull request conflicts with the following ones:
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. |
Encountering this timeout daily. Latest one, locally: test output
|
Does the timeout happen even if just one block is created per call to |
For me, yes, that doesn't resolve it. - self.nodes[0].generate(10)
+ self.nodes[0].generate(1) |
It seems excessive to take 30 seconds (or 240 seconds) for a single block to be generated. The bottleneck should be benchmarked |
in the combined log it looks like a deadlock/hang |
Concept ACK I am getting the same errors when running via test runner. |
f946eb1
to
12a675c
Compare
Did more testing and bumping the timeout from the default 60 to only 120 (instead of 480) appears to be enough to resolve the issue for me locally. If the CI is green, we could start with that. Tested at each point with both 1 and 10 blocks generated and didn't see a difference in timeout behavior. Edit: even a value of 90 resolves the issue for me locally. |
12a675c
to
d09120b
Compare
This was pretty much the only green CI on bitcoinbuilds of the past day out of a few dozen cases. Re-pushed to try lowering the timeout from 120 seconds to only 90, which seems to be sufficient to fix the issue for me locally. |
bitcoinbuilds currently fails with |
Would really like to see this solved, as I'm hitting this issue every day since #20536 was merged on March 8, 2021. I'll open an issue. |
Ok, merging. Though I think this should be investigated. Generating a block shouldn't take several minutes |
Thanks. What is weird: https://bitcoinbuilds.org/index.php?build=8465 is (thankfully) green for the last push, which is the first passing CI there since the previous push. |
Maybe @jonasschnelli updated something...we'll see with the next CI runs. |
I tried reproducing this locally and on HDD I got It would be good to have steps to reproduce or otherwise investigate this. The patch here is only meant as a temporary workaround. |
to hopefully fix timeouts from a new test added in 48a0319 of #20536 merged March 8, 2021
seen locally when running via the test runner
and in the CI like https://bitcoinbuilds.org/index.php?ansilog=28537952-2c92-46f2-9871-8918e5ba2738.log#l2398