Skip to content

test: stability of test_sign_contention_5_nodes#686

Draft
jakmeier wants to merge 3 commits intosig-net:developfrom
jakmeier:stability_of_test_sign_requests_wait_for_presignatures
Draft

test: stability of test_sign_contention_5_nodes#686
jakmeier wants to merge 3 commits intosig-net:developfrom
jakmeier:stability_of_test_sign_requests_wait_for_presignatures

Conversation

@jakmeier
Copy link
Copy Markdown
Contributor

@jakmeier jakmeier commented Mar 5, 2026

  • increase stockpile_max to have more T+P generations in parallel
  • increase time for T+P generation by 1 min
  • increase time for signature generation by 1 min

None of these are perfect solutions.
The generation really should be faster.
But this might help with sporadic CI error that we currently face.

- increase stockpile_max to have more T+P generations in parallel
- increase time for T+P generation by 1 min
- increase time for signature generation by 1 min

None of these are perfect solutions.
The generation really should be faster.
But this might help with sporadic CI error that we currently face.
@jakmeier
Copy link
Copy Markdown
Contributor Author

jakmeier commented Mar 5, 2026

It's not looking great for test_sign_contention_5_nodes stability`.

At least run 1 was successful. (test_signature_rogue did hit a documented race condition but that is unrelated)

But already run 2 hits a signature generation timeout again in test_sign_contention_5_nodes

jakmeier added 2 commits March 5, 2026 15:44
Tokio futures should not run for long.
The poke on triples may take several seconds of CPU time.
During this time, other tasks on the same executor will be blocked.

Spawning the work to a separate thread avoids this issue.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant