Fix flaky test: TestO11y/http_with_token

[circleci-app]

🔧 Flaky Tests Analysis & Fixes

This PR contains a fix for one flaky test that was causing reliability issues due to timing-based race conditions.

📋 Tests Fixed

• o11y/otel/otel_test.go: Fixed race condition in TestO11y/http_with_token subtest by adding proper polling pattern for trace retrieval from Jaeger

⚠️ Tests Analyzed But Not Fixed

None. The single analyzed test was successfully fixed.

🛠️ Types of Changes Made

• Timing fixes: 1 test affected (added polling pattern to eliminate race condition)

🔍 Common Patterns Identified

The test exhibited timing-based flakiness due to a race condition between trace creation/flushing and trace retrieval from Jaeger. The fix involved implementing a proven polling pattern already used elsewhere in the codebase.

✅ Expected Impact

This targeted fix should improve test reliability by addressing the race condition where the "find trace" subtest was directly querying Jaeger without waiting for traces to be indexed, causing intermittent failures when Jaeger hadn't processed the traces yet.

---

Total Tests Analyzed: 1 | Successfully Fixed: 1 | Test Files Modified: 1 | Total Cost: $0.89 | Generated: 2025-08-06

[pete-woods]

Suggested change

	if len(traces) >= 1 {
	return poll.Success()
	}
	return poll.Continue("only got %d traces", len(traces))
	return poll.Compare(cmp.Len(traces, 1))