golang/go

runtime:cpu1: TestPreemptionAfterSyscall/100µs failures

Open

#72,965 建立於 2025年3月20日

在 GitHub 查看
 (75 留言) (0 反應) (0 負責人)Go (133,883 star) (19,008 fork)batch import
AutomationNeedsInvestigationcompiler/runtimehelp wanted

描述

#!watchflakes
default <- pkg == "runtime:cpu1" && test == "TestPreemptionAfterSyscall/100µs"

Issue created automatically to collect these failures.

Example (log):

=== RUN   TestPreemptionAfterSyscall/100µs
    proc_test.go:1082: timeout exceeded: 6.015091541s (5s)
--- FAIL: TestPreemptionAfterSyscall/100µs (12.08s)

— watchflakes

貢獻者指南

技術棧
go
領域
backendperformance
議題類型
bug
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
5
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
over 1 week
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
active
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
needs investigation
前置要求
Go programmingRuntime scheduler concepts
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
10
研究方向
Investigate the flaky test 'TestPreemptionAfterSyscall/100µs' in proc test.go. The test times out, indicating a possible issue with goroutine preemption during syscall. Review recent commits to the Go scheduler (e.g., runtime/proc.go) and related issues. Check if the failure is platform specific (cpu1) and try to reproduce locally. Look for discussions in the comments for hypotheses about root causes or proposed fixes.