[Prometheus Compliance Tests] - Incorrect workflow status during failure

[vasireddy99]

Description

The Prometheus compliance workflow are reporting incorrect status when the tests have a Failure,
reference. This will not help to identify which change has broke the tests.

Expected Result

The workflow should be shown as failure with error when tests are FAIL

Actual Result

The workflow is success when tests are FAIL

[bryan-aguilar]

The exit code of the step will be determined by this line

go test -v --tags=compliance -run "TestRemoteWrite/otel/.+" ./ |& tee ./test-report.txt

I am not familiar with the |& but what I assume this is giving an exit code 0 from the tee when we expect the exit code to be 1 from the go test. This behavior should be able to be replicated locally by running the above command and then checking exit code with echo $?.

[github-actions]

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

• issue: Github issue template generation code needs this to generate the corresponding labels.

See Adding Labels via Comments if you do not have permissions to add labels yourself.

[github-actions]

This issue has been closed as inactive because it has been stale for 120 days with no activity.