golang/go

runtime:cpu4: TestUsingVDSO failures

Open

#67,383 opened on May 15, 2024

View on GitHub
 (3 comments) (0 reactions) (0 assignees)Go (19,008 forks)batch import
NeedsInvestigationcompiler/runtimehelp wanted

Repository metrics

Stars
 (133,883 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

#!watchflakes
default <- pkg == "runtime:cpu4" && test == "TestUsingVDSO"

Issue created automatically to collect these failures.

Example (log):

=== RUN   TestUsingVDSO
=== PAUSE TestUsingVDSO
=== CONT  TestUsingVDSO
    vdso_test.go:51: GO_WANT_HELPER_PROCESS=1 /bin/strace -f -e clock_gettime /home/swarming/.swarming/w/ir/x/t/go-build3885972143/b001/runtime.test -test.run=^TestUsingVDSO$
    vdso_test.go:57: /bin/strace: Process 140051 attached
        /bin/strace: Process 140052 attached
        /bin/strace: Process 140050 attached
        /bin/strace: Process 140053 attached
        [pid 140050] ???( <unfinished ...>
        [pid 140049] --- stopped by SIGURG ---
        /bin/strace: ptrace(PTRACE_LISTEN,pid:140049,sig:0): Input/output error
        /bin/strace: Process 140049 detached
        /bin/strace: Process 140051 detached
        /bin/strace: Process 140052 detached
        /bin/strace: Process 140050 detached
        /bin/strace: Process 140053 detached
    vdso_test.go:70: exit status 1
--- FAIL: TestUsingVDSO (0.14s)

— watchflakes

Contributor guide

Research direction
Investigate the strace error 'ptrace(PTRACE LISTEN, ...): Input/output error' occurring in TestUsingVDSO. The test uses strace to trace clock gettime syscalls, and a SIGURG signal seems to interrupt ptrace. Look into how the VDSO is used and why strace fails; possibly a race condition or kernel interaction.
Tech stack
go
Domain
backend
Issue type
Bug
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.
Half day
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
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30