e2e: consider adding a second kubo node and run the test offline #1131
Labels
effort/days
Estimated to take multiple days, but less than a week
exp/beginner
Can be confidently tackled by newcomers
kind/enhancement
A net-new feature or improvement to an existing feature
kind/maintenance
Work required to avoid breaking changes or harm to project's status quo
kind/test
Testing work
P3
Low: Not priority right now
status/ready
Ready to be worked
topic/ci
Continuous integration
If we had 2 Kubo nodes running in the E2E setup, we would be able to run the tests offline, because this would guarantee each Kubo node has peers to discover.
See #1121 (comment)
The text was updated successfully, but these errors were encountered: