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

Node-test is failing in Github Actions CI #2434

Closed
3 tasks
abitmore opened this issue Apr 28, 2021 · 1 comment · Fixed by #2445
Closed
3 tasks

Node-test is failing in Github Actions CI #2434

abitmore opened this issue Apr 28, 2021 · 1 comment · Fixed by #2445

Comments

@abitmore
Copy link
Member

abitmore commented Apr 28, 2021

Build Error Description

Nodes are now unable to sync in Github Actions CI. See https://github.com/bitshares/bitshares-core/runs/2453471122 .

It was fine yesterday. See https://github.com/bitshares/bitshares-core/runs/2448441028 .

When debugging, found suspicious messages in p2p.log (see https://github.com/abitmore/bitshares-core/runs/2458242069):

p2p:message read_loop on_item_not_availabl ] Peer doesn't have the requested sync item. This really shouldn't happen

Note: the default seed nodes have been updated, so node-test is passing in Github Actions CI, but the real fix is #2445.

This Ci job reproduces the issue: https://github.com/abitmore/bitshares-core/runs/2491471762 ,
this CI job verifies the fix proposed in #2445: https://github.com/abitmore/bitshares-core/runs/2491784005 (note: the log files are large).

CORE TEAM TASK LIST

  • Evaluate Build Error
  • Provide build guidance
  • Create Bug Report
@abitmore
Copy link
Member Author

abitmore commented May 3, 2021

Fixed by #2445.

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 a pull request may close this issue.

1 participant