[Flaky test] TestGenerateProcessorList: `panic: Log in goroutine after TestGenerateProcessorList has completed`

[belimawr]

Flaky Test

• Test Name: TestGenerateProcessorList
• Link:

  beats/libbeat/publisher/processing/default_test.go

  Line 43 in 0e87812

  func TestGenerateProcessorList(t *testing.T) {

• Branch: 8.19
• Artifact Link: https://buildkite.com/elastic/beats-libbeat/builds/22868/steps/canvas?sid=019a5537-1fc0-4bfb-8159-14fba7e6503d#019a554e-27e6-43d1-8d05-100be1d8dc14/193-592
• Notes: The root cause is also present on main, but the panic has been mitigated by using a no-op logger. See Fix all tests/components that fail with panic: Log in goroutine after TestXXX has completed #47527 for more details.

Stack Trace

2025-11-05 13:54:43 EST
panic: Log in goroutine after TestGenerateProcessorList has completed: 2025-11-05T18:46:23.758Z	DEBUG	add_cloud_metadata	add_cloud_metadata: received disposition for hetzner after 3.764475ms. result=[provider:hetzner, error=failed with http status code 404, metadata={}]
2025-11-05 13:54:43 EST
	panic: Log in goroutine after TestGenerateProcessorList has completed: 2025-11-05T18:46:23.758Z	DEBUG	add_cloud_metadata	add_cloud_metadata: fetchMetadata ran for 3.818102ms
2025-11-05 13:54:43 EST

[elasticmachine]

Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane)

[khushijain21]

Another Instance https://buildkite.com/elastic/beats-libbeat/builds/23446#019aa149-88fb-4b51-b203-9468233d27dc

[kruskall]

Should be fixed by #47661, #47662 and #47663