fix(test): use port 0 instead of hardcoded 9101 in TCP warning test
Some checks failed
CI / test (push) Failing after 3s
Some checks failed
CI / test (push) Failing after 3s
Port 9101 conflicts with running core-agent serve. OS-assigned port avoids the conflict and still tests the 0.0.0.0 warning. Co-Authored-By: Virgil <virgil@lethean.io>
This commit is contained in:
parent
1d44728dcd
commit
c815b9f1b1
1 changed files with 2 additions and 2 deletions
|
|
@ -37,8 +37,8 @@ func TestNewTCPTransport_Warning(t *testing.T) {
|
|||
old := setDiagWriter(&buf)
|
||||
defer setDiagWriter(old)
|
||||
|
||||
// Trigger warning
|
||||
tr, err := NewTCPTransport("0.0.0.0:9101")
|
||||
// Trigger warning — use port 0 (OS assigns free port)
|
||||
tr, err := NewTCPTransport("0.0.0.0:0")
|
||||
if err != nil {
|
||||
t.Fatalf("Failed to create transport: %v", err)
|
||||
}
|
||||
|
|
|
|||
Loading…
Add table
Reference in a new issue