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

ddo: lotus devnet reports the same miner ID for all miners #1718

Closed
dirkmc opened this issue Sep 26, 2023 · 1 comment
Closed

ddo: lotus devnet reports the same miner ID for all miners #1718

dirkmc opened this issue Sep 26, 2023 · 1 comment
Assignees

Comments

@dirkmc
Copy link
Contributor

dirkmc commented Sep 26, 2023

Boost's direct data onboarding branch depends on lotus commit 4afb22466d7a.

It seems that in that lotus commit, when we create two miners using the itest framework they both report the same miner ID:

2023-09-14T12:56:16.161+0200	INFO	booster	lib/api.go:74	Using storage API at ws://127.0.0.1:58229/rpc/v0
2023-09-14T12:56:16.163+0200	INFO	booster	lib/api.go:198	Miner address: f01000
2023-09-14T12:56:16.165+0200	INFO	booster	lib/api.go:74	Using storage API at ws://127.0.0.1:58243/rpc/v0
2023-09-14T12:56:16.166+0200	INFO	booster	lib/api.go:198	Miner address: f01000

This causes our multi-miner tests to fail.

We need to dig into why this is happening , probably with the help of the lotus team .

@nonsense nonsense moved this to In Progress in Boost Oct 2, 2023
@nonsense nonsense self-assigned this Oct 2, 2023
@nonsense
Copy link
Member

nonsense commented Oct 4, 2023

Fixed.

@nonsense nonsense closed this as completed Oct 4, 2023
@github-project-automation github-project-automation bot moved this from In Progress to Done in Boost Oct 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

No branches or pull requests

2 participants