Closed belimawr closed 3 months ago
Pinging @elastic/sec-linux-platform (Team:Security-Linux Platform)
Pinging @elastic/sec-windows-platform (Team:Security-Windows Platform)
It looks like this is a result of netsh now emitting version information and this not being properly handled by the helper since it was unknown behaviour.
=== FAIL: packetbeat/route TestDefault (0.95s)
route_test.go:38: unexpected error from defaultRoute(23): unexpected netsh line: "netsh.exe: version 10.0.20348.1"
Publish Type Met Prefix Idx Gateway/Interface Name
------- -------- --- ------------------------ --- ------------------------
No System 256 ::1/128 1 Loopback Pseudo-Interface 1
No System 256 fe80::/64 4 Ethernet
No System 256 fe80::/64 9 vEthernet (nat)
No System 256 fe80::557:e168:e133:5781/128 9 vEthernet (nat)
No System 256 fe80::e58d:ff83:e072:e694/128 4 Ethernet
No System 256 ff00::/8 1 Loopback Pseudo-Interface 1
No System 256 ff00::/8 4 Ethernet
No System 256 ff00::/8 9 vEthernet (nat)
netsh.exe: version 10.0.20348.1
Flaky Test
Test Name: TestDefault
Link: https://github.com/elastic/beats/blob/43d5dd4342a9ff56f40fafe1ba2ad7ed0a03b6c3/packetbeat/route/route_windows_test.go#L63
Branch: main
Artifact Link:
Notes: It started failing consistently on
main
after https://github.com/elastic/beats/commit/62b4c18f2c13921814ee133f3ec4d44fe69ceba9 was merged. However this commit only removed two debug log lines from Filebeat. I cannot see any correlation between this commit and the Packetbeat test panic.Stack Trace
When I run the same tests on Linux I get an error instead of a panic:
I also tested it on my Windows machine and it passed, even with 100 repetitions.