-
Notifications
You must be signed in to change notification settings - Fork 15
Conversation
Updates deps and adds types to tests. BREAKING CHANGE: needs ESM release of ipfs/libp2p
3f4f269
to
11dd674
Compare
11dd674
to
29e3775
Compare
2022-09-09T14:33:52.431Z ipfsd-ctl:daemon:stderr 2022-09-09T14:33:52.420Z ERROR provider.queue queue/queue.go:124 Failed to enqueue cid: leveldb: closed This is a red herring, there's no error like this with [email protected] but it's still broken. |
The problem is that the relay daemon doesn't always start up. This build passed - https://github.com/ipfs/interop/actions/runs/3024182787/attempts/1 - I restarted the build, no changes between and it failed: https://github.com/ipfs/interop/actions/runs/3024182787/attempts/2 Successful (notice
Failure (notice no
|
Working test run with GOLOG_LOG_LEVEL: https://github.com/ipfs/interop/runs/8277122415?check_suite_focus=true Failed test run with GOLOG_LOG_LEVEL: https://github.com/ipfs/interop/runs/8277153592?check_suite_focus=true Things missing from the failed run that are found in the successful run:
|
The most interesting part seems to be the lines between 'REUSEPORT' and
What starts the "generating peer identity" log entry, and why is there no failure in the failed workflow?
What starts the "initializing new limiter with config" log entry, and why is there no failure in the failed workflow?
|
Set |
This seems to be a combination of issues.
To fix 1 I've made relay daemon use a random temporary file for it's identity so it's guaranteed to create a new peer id on every run. To fix 2 I've made the relay daemon setup script download the daemon binary on-demand, similar to how aegir downloads electron on-demand when it's first used. I've applied these fixes to #462 which should hopefully start to look a bit more healthy now. |
Thank you @achingbrain ❤️ I assume this PR is no longer useful – closing. |
This PR is a sandbox to try to fix
circuit
go-rv1-go
test that fails on CI: