[receiver/faroreceiver]: Report for failed tests on main

[github-actions]

Auto-generated report for __run_3 job build.

Link to failed build: https://github.com/open-telemetry/opentelemetry-collector-contrib/actions/runs/15279388990

Test Failures

• TestComponentLifecycle/traces-lifecycle
• TestComponentLifecycle

Note: Information about any subsequent build failures that happen while
this issue is open, will be added as comments with more information to this issue.

[github-actions]

Pinging code owners for receiver/faro: @dehaansa @rlankfo @mar4uk. See Adding Labels via Comments if you do not have permissions to add labels yourself. For example, comment '/label priority:p2 -needs-triaged' to set the priority and remove the needs-triaged label.

[github-actions]

Link to latest failed build: https://github.com/open-telemetry/opentelemetry-collector-contrib/actions/runs/15279395353

Test Failures

• TestComponentLifecycle/logs-lifecycle
• TestComponentLifecycle

[dehaansa]

@ArthurSens am I missing something here, I don't see any test failures on the initial link, and the second one is integration test failures for dockerhub rate limiting that don't appear to have any faro tests involved.

[ArthurSens]

Hey @dehaansa, I was able to find the test failures, but I agree they are hard to find 😬. Right now, it requires searching through logs from successful workflow runs.

https://github.com/open-telemetry/opentelemetry-collector-contrib/actions/runs/15279388990/job/42974204919

The workflow itself is not marked as failed anymore, because we're using continue-on-error[1]. We need that option because the following jobs/steps wouldn't run otherwise, but it has this downside of always marking the workflow as successful 😕

[ArthurSens]

Not sure how to do it, but we could try to think of strategies to make the experience here a bit better. Some ideas:

• Provide the error message in the Github comment
• Add /job/<job-id> to the link that is added to the comment

[dehaansa]

Ah, I see. Error message in github issue would be good, or at very minimum a note that the workflow currently has to mark as successful so we know we have to dig!

[github-actions]

Link to latest failed build: https://github.com/open-telemetry/opentelemetry-collector-contrib/actions/runs/15294854309

Test Failures

• TestComponentLifecycle/logs-lifecycle
• TestComponentLifecycle
• TestFaroReceiver_Start

[dehaansa]

New failure (TestFaroReceiver_Start) is likely a symptom of the same shutdown behavior as fixed in the linked PR, dug in (faro fulls under receiver-0 group, this failure was in go 1.23) and saw the same error message (port 8080 already bound)

[github-actions]

Link to latest failed build: https://github.com/open-telemetry/opentelemetry-collector-contrib/actions/runs/15301214093

Test Failures

• TestComponentLifecycle/logs-lifecycle
• TestComponentLifecycle
• TestFaroReceiver_Start

[github-actions]

Link to latest failed build: https://github.com/open-telemetry/opentelemetry-collector-contrib/actions/runs/15327044974

Test Failures

• TestFaroReceiver_Start