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

Test Failure: restart-scenarios-test-hard_replay #144

Closed
heifner opened this issue May 15, 2024 · 2 comments
Closed

Test Failure: restart-scenarios-test-hard_replay #144

heifner opened this issue May 15, 2024 · 2 comments
Labels
test-instability tag issues for flaky tests, high priority to address

Comments

@heifner
Copy link
Member

heifner commented May 15, 2024

https://github.com/AntelopeIO/spring/actions/runs/9100452880/job/25015943882

  File "/__w/spring/spring/build/tests/restart-scenarios-test.py", line 52, in <module>
    if cluster.launch(pnodes=pnodes, totalNodes=total_nodes, topo=topo, delay=delay, activateIF=activateIF) is False:
  File "/__w/spring/spring/build/tests/TestHarness/Cluster.py", line 532, in launch
    if not self.bootstrap(launcher, self.biosNode, self.startedNodesCount, prodCount + sharedProducers, totalProducers, pfSetupPolicy, onlyBios, onlySetProds, loadSystemContract, activateIF, biosFinalizer, signatureProviderForNonProducer):
  File "/__w/spring/spring/build/tests/TestHarness/Cluster.py", line 1194, in bootstrap
    ret=Utils.waitForBool(lam)
  File "/__w/spring/spring/build/tests/TestHarness/testUtils.py", line 271, in waitForBool
    ret=Utils.waitForObj(myLam, timeout, sleepTime, reporter=reporter)
  File "/__w/spring/spring/build/tests/TestHarness/testUtils.py", line 261, in waitForObj
    raise RuntimeError('waitForObj reached 60 second timeout')
RuntimeError: waitForObj reached 60 second timeout

A quick look it appears that node_00 was not able to establish a connection to peers at startup. By the time it was able to connect and sync, its last synced block had latency: 9183 ms which is too much for it to start producing. Since it doesn't produce the test times out waiting. node_00 has producers: defproducera - defproducerf.

@enf-ci-bot enf-ci-bot moved this to Todo in Team Backlog May 15, 2024
@arhag arhag added test-instability tag issues for flaky tests, high priority to address and removed triage labels May 15, 2024
@arhag
Copy link
Member

arhag commented Jul 26, 2024

Might be related to #399?

@bhazzard
Copy link

Haven't seen this fail recently.

@bhazzard bhazzard closed this as not planned Won't fix, can't repro, duplicate, stale Oct 17, 2024
@github-project-automation github-project-automation bot moved this from Todo to Done in Team Backlog Oct 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
test-instability tag issues for flaky tests, high priority to address
Projects
Status: Done
Development

No branches or pull requests

4 participants