golang/go

runtime:cpu1: TestPreemptionAfterSyscall/1ms failures

Open

#71181 opened on Jan 8, 2025

View on GitHub
 (42 comments) (0 reactions) (0 assignees)Go (133,883 stars) (19,008 forks)batch import
AutomationNeedsInvestigationcompiler/runtimehelp wanted

Description

#!watchflakes
default <- pkg == "runtime:cpu1" && test == "TestPreemptionAfterSyscall/1ms"

Issue created automatically to collect these failures.

Example (log):

=== RUN   TestPreemptionAfterSyscall/1ms
    proc_test.go:1082: timeout exceeded: 5.044309084s (5s)
--- FAIL: TestPreemptionAfterSyscall/1ms (5.10s)

— watchflakes

Contributor guide

Tech stack
go
Domain
performance
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
5
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
over 1 week
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
Go runtime knowledgepreemption conceptsscheduling
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
5
Research direction
Examine proc test.go line 1082 and the TestPreemptionAfterSyscall test. Investigate why the test times out after a syscall. Look for recent changes to the runtime preemption mechanism or scheduler that could affect timing. Review linked logs and comments for patterns.