Skip to content
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

fix: tests: Make TestWorkerKeyChange not flaky #10320

Merged
merged 1 commit into from
Feb 20, 2023

Conversation

magik6k
Copy link
Contributor

@magik6k magik6k commented Feb 20, 2023

Related Issues

Proposed Changes

Additional Info

Checklist

Before you mark the PR ready for review, please make sure that:

  • Commits have a clear commit message.
  • PR title is in the form of of <PR type>: <area>: <change being made>
    • example: fix: mempool: Introduce a cache for valid signatures
    • PR type: fix, feat, build, chore, ci, docs, perf, refactor, revert, style, test
    • area, e.g. api, chain, state, market, mempool, multisig, networking, paych, proving, sealing, wallet, deps
  • New features have usage guidelines and / or documentation updates in
  • Tests exist for new functionality or change in behavior
  • CI is green

@magik6k magik6k requested a review from a team as a code owner February 20, 2023 16:41
Comment on lines +37 to +38
blocktime := 5 * time.Millisecond
client1, miner, ens := kit.EnsembleMinimal(t, kit.MockProofs())
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There was zero reason this test had two nodes, and with the really low block time, on lower-perf instance it was possible that the second node never caught up

@arajasek arajasek merged commit 392d3d4 into master Feb 20, 2023
@arajasek arajasek deleted the fix/flaky-workerkeychange branch February 20, 2023 17:47
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.

2 participants