[Flaky Test]: TestContainerCMDEventToStderr – cannot find events on stderr

[belimawr]

Failing test case

TestContainerCMDEventToStderr

Error message

cannot find events on stderr

Build

https://buildkite.com/elastic/elastic-agent/builds/17929#01955d14-9147-4200-9f43-716a76457a8b

OS

Linux

Stacktrace and notes

2025-03-03 12:53:25 EST	=== FAIL: testing/integration TestContainerCMDEventToStderr (213.77s)
2025-03-03 12:53:25 EST	    fetcher.go:93: Using existing artifact elastic-agent-9.0.0-SNAPSHOT-linux-x86_64.tar.gz
2025-03-03 12:53:25 EST	    fixture.go:290: Extracting artifact elastic-agent-9.0.0-SNAPSHOT-linux-x86_64.tar.gz to /tmp/TestContainerCMDEventToStderr4061749239
2025-03-03 12:53:25 EST	    fixture.go:308: Completed extraction of artifact elastic-agent-9.0.0-SNAPSHOT-linux-x86_64.tar.gz to /tmp/TestContainerCMDEventToStderr4061749239
2025-03-03 12:53:25 EST	    fixture.go:908: Components were not modified from the fetched artifact
2025-03-03 12:53:25 EST	    container_cmd_test.go:75: Creating enrollment API key...
2025-03-03 12:53:25 EST	    container_cmd_test.go:360: >> running binary with: [/tmp/TestContainerCMDEventToStderr4061749239/elastic-agent-9.0.0-SNAPSHOT-linux-x86_64/elastic-agent container]
2025-03-03 12:53:25 EST	    fixture.go:665: >> running binary with: [/tmp/TestContainerCMDEventToStderr4061749239/elastic-agent-9.0.0-SNAPSHOT-linux-x86_64/elastic-agent status --output json]
2025-03-03 12:53:25 EST	    fixture.go:665: >> running binary with: [/tmp/TestContainerCMDEventToStderr4061749239/elastic-agent-9.0.0-SNAPSHOT-linux-x86_64/elastic-agent status --output json]
2025-03-03 12:53:25 EST	    fixture.go:665: >> running binary with: [/tmp/TestContainerCMDEventToStderr4061749239/elastic-agent-9.0.0-SNAPSHOT-linux-x86_64/elastic-agent status --output json]
2025-03-03 12:53:25 EST	    fixture.go:665: >> running binary with: [/tmp/TestContainerCMDEventToStderr4061749239/elastic-agent-9.0.0-SNAPSHOT-linux-x86_64/elastic-agent status --output json]
2025-03-03 12:53:25 EST	    fixture.go:665: >> running binary with: [/tmp/TestContainerCMDEventToStderr4061749239/elastic-agent-9.0.0-SNAPSHOT-linux-x86_64/elastic-agent status --output json]
2025-03-03 12:53:25 EST	    fixture.go:665: >> running binary with: [/tmp/TestContainerCMDEventToStderr4061749239/elastic-agent-9.0.0-SNAPSHOT-linux-x86_64/elastic-agent status --output json]
2025-03-03 12:53:25 EST	    fixture.go:665: >> running binary with: [/tmp/TestContainerCMDEventToStderr4061749239/elastic-agent-9.0.0-SNAPSHOT-linux-x86_64/elastic-agent status --output json]
2025-03-03 12:53:25 EST	    container_cmd_test.go:380:
2025-03-03 12:53:25 EST	        	Error Trace:	/opt/buildkite-agent/builds/bk-agent-prod-gcp-1741023606852710434/elastic/elastic-agent/testing/integration/container_cmd_test.go:380
2025-03-03 12:53:25 EST	        	Error:      	Condition never satisfied
2025-03-03 12:53:25 EST	        	Test:       	TestContainerCMDEventToStderr
2025-03-03 12:53:25 EST	        	Messages:   	cannot find events on stderr
2025-03-03 12:53:25 EST	    container_cmd_test.go:98: >> cleaning up: killing the Elastic-Agent process
2025-03-03 12:53:25 EST	    fixture.go:1284: Temporary directory "/tmp/TestContainerCMDEventToStderr4061749239" preserved for investigation/debugging
2025-03-03 12:53:25 EST

[elasticmachine]

Pinging @elastic/elastic-agent (Team:Elastic-Agent)

[belimawr]

Failing PR: #6730

[belimawr]

This test seems to be consistent failing in the PR above I even managed to reproduce it on my machine, but it is passing on main. I'll investigate this further.

My PR seems unrelated to this test because it only adds a condition to a monitoring processor. Anyways, I'll investigate more tomorrow.