Currently, BulwarkProcessor
can fail silently if it tries to bind to a port already in use
#274
Labels
kind/bug
Categorizes issue or PR as related to a bug.
kind/testing
Categorizes issue or PR as related to testing.
kind/usability
Categorizes issue or PR as related to improving some aspect of usability.
Milestone
Notably this can happen in the integration tests, since they currently use the default port. The port used by tests should probably be changed to avoid this collision with dev servers, but also tests should fail much earlier if this happens.
The text was updated successfully, but these errors were encountered: