open-telemetry/opentelemetry-collector

flaky test TestBatchSender_InvalidMergeSplitFunc on windows

Open

#10,841 opened on Aug 8, 2024

View on GitHub
 (0 comments) (0 reactions) (1 assignee)Go (2,146 forks)auto 404
area:exporterflaky testhelp wantedos:windows

Repository metrics

Stars
 (7,237 stars)
PR merge metrics
 (PR metrics pending)

Description

See additional details https://github.com/open-telemetry/opentelemetry-collector/actions/runs/10303739944/job/28520527637?pr=10837

--- FAIL: TestBatchSender_InvalidMergeSplitFunc (0.11s)
    batch_sender_test.go:255: 
        	Error Trace:	D:/a/opentelemetry-collector/opentelemetry-collector/exporter/exporterhelper/batch_sender_test.go:255
        	Error:      	Condition never satisfied
        	Test:       	TestBatchSender_InvalidMergeSplitFunc
FAIL
FAIL	go.opentelemetry.io/collector/exporter/exporterhelper	1.677s

Contributor guide

Research direction
Investigate the flaky test TestBatchSender InvalidMergeSplitFunc on Windows. Look for timing or race conditions in the test logic that may cause the condition never satisfied error. Check if the test relies on goroutine scheduling or timeouts that differ on Windows.
Tech stack
go
Domain
backendtesting
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.
Needs investigation
Prerequisites
Gotesting
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60