chore(test): make failures in TestRemoteWrite_PerQueueMetricsAfterRelabeling

more explicit to help with debugging the test when it flakes for GOARCH=386

tried to make it fail in the CI running the following, in vain:

GOARCH=386 go test --timeout 4444444s --count=1000 --run=TestRemoteWrite_PerQueueMetricsAfterRelabeling ./cmd/prometheus/

Signed-off-by: machine424 <ayoubmrini424@gmail.com>
This commit is contained in:
machine424 2025-10-17 14:32:04 +02:00
parent 1751685dd4
commit dfea5ef01a
No known key found for this signature in database
GPG key ID: A4B001A4FDEE017D

View file

@ -890,8 +890,10 @@ func TestRemoteWrite_PerQueueMetricsAfterRelabeling(t *testing.T) {
port := testutil.RandomUnprivilegedPort(t)
targetPort := testutil.RandomUnprivilegedPort(t)
server := httptest.NewServer(http.HandlerFunc(func(http.ResponseWriter, *http.Request) {
panic("should never be reached")
server := httptest.NewServer(http.HandlerFunc(func(_ http.ResponseWriter, r *http.Request) {
body, err := io.ReadAll(r.Body)
require.NoError(t, err)
require.Fail(t, "should never be reached because the remote write relabeling shouldn't yield anything", "header: %v, body: %s", r.Header, body)
}))
t.Cleanup(server.Close)