Skip to content

[Flaky Test] TestStandAloneRunningSuite/TestOpAMP signal: killed #6590

@ebeahan

Description

@ebeahan

Flaky Test

Claude Code analysis

The single failing test is TestStandAloneRunningSuite/TestOpAMP. It fails with signal: killed at stand_alone_test.go:659, which is the Require().NoError(err) after the make otelcontribcol call.

The cause is straightforward: the test runs under a 3-minute context timeout (context.WithTimeout(..., 3*time.Minute) at line 603), but it tries to do all of this within that window:

  1. Clone the entire opentelemetry-collector-contrib repo (shallow, but still large)
  2. Run make otelcontribcol — a full Go compilation of a massive multi-module project
  3. Enroll an agent, start the OTel collector, and verify enrollment

Compiling OTel contrib from scratch on a resource-constrained CI agent can easily take 5–15 minutes. When the 3-minute deadline expires, Go's exec.CommandContext sends SIGKILL to the build process, and the temp directory gets cleaned up mid-compile, causing the cascading "no such file or directory" errors seen in the log.

Stack Trace

Error Trace:	/opt/buildkite-agent/builds/bk-agent-prod-gcp-1773340912775914247/elastic/fleet-server/testing/e2e/stand_alone_test.go:659

            				/opt/buildkite-agent/.gvm/versions/go1.25.8.linux.amd64/src/runtime/asm_amd64.s:1693

Error:      	Received unexpected error:

            	signal: killed

Test:       	TestStandAloneRunningSuite/TestOpAMP

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No fields configured for Task.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions