-
Notifications
You must be signed in to change notification settings - Fork 677
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
Experiment with timeout for tests::nakamoto_integrations::check_block_info_rewards
#4887
Comments
51 minutes for a failure (works locally in a few minutes). the result was a panic though:
incidentally, |
@obycode after speaking to @jferrant about this specific test - i'm able to reproduce her failures on develop (17d917c). i have the full ouput if needed, but it looks like an assertion error. i've reproduced this with both cargo test and nextest:
|
to reproduce: nexteststandalone
nextext archive (this is similar to how CI will execute the test)
cargo test
|
possible this value is incorrect? https://github.com/stacks-network/stacks-core/blob/develop/testnet/stacks-node/src/tests/nakamoto_integrations.rs#L6435 |
updating that line does pass the test, so i'm not sure if that value is incorrect or the test is off:
|
ah, yes, it's definitely possible that the value is off. I don't think it will definitely be consistent though, so I think we can just check that there is a |
I think i have enough to get some timing here - i'll run some CI tests against the PR'ed branch since that does indeed pass (and won't affect timing at all) |
@obycode with the generic assert, it takes ~20 minutes. i don't expect that to change much with a specific value: |
I just discovered that in tests, the maturation time is just 2 blocks, so this test can be much faster! |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
tests::nakamoto_integrations::check_block_info_rewards
is added in #4846 to the "slow" tests, but it likely will take longer than the 30 minute timeout set for those tests when running in CI. We need to experiment with how long it takes, and then create a new job for this longer timeout.The text was updated successfully, but these errors were encountered: