golang/go

cmd/compile: TestScript/issue77033 failures

Open

#77485 opened on Feb 6, 2026

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

Description

#!watchflakes
default <- pkg == "cmd/compile" && test == "TestScript/issue77033"

Issue created automatically to collect these failures.

Example (log):

=== RUN   TestScript/issue77033
=== PAUSE TestScript/issue77033
=== CONT  TestScript/issue77033
    run.go:226: 2026-02-06T17:48:47Z
    run.go:228: $WORK=C:\b\s\w\ir\x\t\TestScriptissue77033808663770\001
    run.go:235: 
        ALLUSERSPROFILE=C:\ProgramData
        APPDATA=C:\Users\chrome-bot\AppData\Roaming
        AR=ar
        BOTO_CONFIG=C:\b\s\w\ir\x\a\gsutil-bbagent\.boto
...
        [stdout]
        goos: windows
        goarch: amd64
        pkg: demo
        cpu: Intel(R) Xeon(R) CPU @ 2.00GHz
        BenchmarkFoo-16    	 8263204	       153.4 ns/op
        PASS
        ok  	demo	1.441s
    run.go:235: FAIL: testdata\script\issue77033.txt:2: go test -bench=Foo -pgo=default.pgo: exec: canceling Cmd: not supported by windows
--- FAIL: TestScript/issue77033 (334.11s)

— watchflakes

Contributor guide

Tech stack
go
Domain
testing
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
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.
clear
Prerequisites
Go programmingWindows environmenttest script understanding
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
45
Research direction
Investigate the test script 'testdata/script/issue77033.txt' in the Go compiler repository. The failure occurs on Windows because the exec.Cmd canceling functionality is not supported. Review the test setup and the go test command with pgo flag. Check if there is a way to skip the test on Windows or to implement the missing functionality. Consider looking at existing platform specific test skips in the codebase. Also review comments in issue #77485 for any insights from maintainers.