Open sharbuz opened 9 months ago
Pinging @elastic/sec-linux-platform (Team:Security-Linux Platform)
During the migration of beats-ci from Jenkins to Buildkite, a number of tests were failing consistently due to issues unrelated to the migration. Those tests were disabled to stabilize the CI, with the intent to revisit them post-migration. @oakrizan has reviewed them all in her draft PRs linked above in the description, and has opened tickets such as this one to highlight to the product teams the tests that are currently still disabled and could use some attention.
Failed Test
Test Name: TestDevices
Link: https://github.com/elastic/beats/blob/7b041ba327011d85471cfd37f1014f054ae43436/x-pack/packetbeat/tests/system/app_test.go#L55-L70
Branch: main: https://github.com/elastic/beats/pull/40387
Artifact Link: beats-xpack-packetbeat_build_5706_windows-x-pack-slash-packetbeat-win-2022-system-tests.log
Notes: Additional details about the test. e.g. theory as to failure cause NB! tests should be enabled back, since those were muted while migrating from Jenkins to Buildkite. Please uncomment: https://github.com/elastic/beats/blob/7b041ba327011d85471cfd37f1014f054ae43436/.buildkite/x-pack/pipeline.xpack.packetbeat.yml#L163 https://github.com/elastic/beats/blob/7b041ba327011d85471cfd37f1014f054ae43436/.buildkite/x-pack/pipeline.xpack.packetbeat.yml#L253
Buildkite builds: https://buildkite.com/elastic/beats-xpack-packetbeat/builds/5706#_
Stack Trace