[Flaky test] Test_ComponentStatusReporting_SharedInstance flaky

Repository metrics

Stars

7,237 stars (7,237 stars)

PR merge metrics

PR metrics pending (PR metrics pending)

Description

--- FAIL: Test_ComponentStatusReporting_SharedInstance (15.01s)
    status_test.go:117: 
        	Error Trace:	D:/a/opentelemetry-collector/opentelemetry-collector/internal/e2e/status_test.go:117
        	Error:      	Not equal: 
        	            	expected: 2
        	            	actual  : 6
        	Test:       	Test_ComponentStatusReporting_SharedInstance
    status_test.go:120: 
        	Error Trace:	D:/a/opentelemetry-collector/opentelemetry-collector/internal/e2e/status_test.go:120
        	Error:      	Not equal: 
        	            	expected: 6
        	            	actual  : 7
        	Test:       	Test_ComponentStatusReporting_SharedInstance
FAIL
FAIL	go.opentelemetry.io/collector/internal/e2e	18.766s
FAIL

Contributor guide

Research direction

Investigate the flaky test by examining the test code and the component under test. Look for timing dependencies or race conditions that cause intermittent failures. Check if recent changes to the component or test environment could introduce flakiness.

Tech stack

go

Domain

backend

Issue type

Test

DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.

2

Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.

1-3 hours

Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.

Active

ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.

Clear

Prerequisites

Go

Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.

70