In some recent CI failures, it seemed that even though only one event was unmatched, the unmatched JSON output included all events. The only way to diagnose this was to add -test.v to the e2e test args. For reference, I'm attaching the logs afer enabling -test.v and artifacts from the same run.
In the logs, you can see that only one event was missed:
2024-10-31T08:59:08.8668768Z time="2024-10-31T08:59:08Z" level=info msg="UnorderedEventChecker: checking pending 1/1: ProcessExecChecker/otel-demo-opensearch: Process check failed: ProcessChecker: Pod check failed: PodChecker: PodLabels[app.kubernetes.io/component] (app.kubernetes.io/component=loadgenerator) check failed: 'loadgenerator' does not match full 'otel-demo-opensearch'"
2024-10-31T08:59:08.8672504Z time="2024-10-31T08:59:08Z" level=info msg="PROCESS_EXEC:3584 => no match: UnorderedEventChecker: all 1 check(s) failed, continuing"
2024-10-31T08:59:09.0824913Z I1031 08:59:09.081023 13892 rpcchecker.go:249] event checker labelsEventChecker timed out after 10m0s
But the in the unmatched json event, all events are unmatched:
In some recent CI failures, it seemed that even though only one event was unmatched, the unmatched JSON output included all events. The only way to diagnose this was to add
-test.vto the e2e test args. For reference, I'm attaching the logs afer enabling-test.vand artifacts from the same run.In the logs, you can see that only one event was missed:
But the in the unmatched json event, all events are unmatched:
labelsEventChecker.eventchecker.events.json labelsEventChecker.eventchecker.log labelsEventChecker.eventchecker.unmatched.json 4ubuntu-22.04-arm64 labels.txt