maybe check/limit ethereal ports (os dep.) and bind to something just outside (but still >1024) that range? so they should be "known free," at least on the local machine

if you haven't yet, check out cloudflare's linux tcp literature! they cover tons of odd edge cases for this kind of stuff

you're talking about port collisions when two tests launch the same service?

id have the service bind to :0 and output somewhere (logs/stdio/oneshot channel/etc) what random port the os gives it, for the test to injest

god damn soul master ass

just got my first phase 2 stagger

this rotten shroom will be defeated

there's not a phase 3 right? team cherry wouldn't do that.. right???