prometheus/prometheus

TestScrapeReportLimit is flaky

Open

#16,906 建立於 2025年7月22日

在 GitHub 查看
 (4 留言) (0 反應) (1 負責人)Go (64,042 star) (10,408 fork)batch import
component/testshelp wantedkind/bugpriority/P2

描述

on windows at least

=== RUN   TestScrapeReportLimit
    scrape_test.go:4028: 
        	Error Trace:	D:/a/prometheus/prometheus/scrape/scrape_test.go:4028
        	Error:      	Not equal: 
        	            	expected: 1
        	            	actual  : 0
        	Test:       	TestScrapeReportLimit
--- FAIL: TestScrapeReportLimit (0.24s)

https://github.com/prometheus/prometheus/actions/runs/16438225686/job/46452599936?pr=16904 if it's still available.

貢獻者指南

技術棧
go
領域
testing
議題類型
bug
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
half day
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
blocked
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
Go programming
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
10
研究方向
Investigate the TestScrapeReportLimit test in scrape test.go. The test fails intermittently on Windows with an assertion expecting 1 but getting 0. Check for race conditions or Windows specific issues. Look at the test's setup and teardown, and consider if adding synchronization or adjusting timeouts would fix it. Review the CI logs from the linked run for more details.
TestScrapeReportLimit is flaky · prometheus/prometheus#16906 | Good First Issue