Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

runtime: TestFreeBSDNumCPU fails #38937

Closed
stevenh opened this issue May 7, 2020 · 2 comments
Closed

runtime: TestFreeBSDNumCPU fails #38937

stevenh opened this issue May 7, 2020 · 2 comments
Labels
FrozenDueToAge NeedsFix The path to resolution is known, but the work has not been done.
Milestone
Go1.15

Comments

@stevenh
Copy link
Contributor

stevenh commented May 7, 2020

What version of Go are you using (go version)?

$ go version go1.14.2 freebsd/amd64

Does this issue reproduce with the latest release?

Yes

What operating system and processor architecture are you using (go env)?

go env Output
$ go env
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/root/.cache/go-build"
GOENV="/root/.config/go/env"
GOEXE=""
GOFLAGS="-v -race"
GOHOSTARCH="amd64"
GOHOSTOS="freebsd"
GOINSECURE=""
GONOPROXY=""
GONOSUMDB=""
GOOS="freebsd"
GOPATH="/root/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/local/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/local/go/pkg/tool/freebsd_amd64"
GCCGO="gccgo"
AR="ar"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
GOMOD="/data/jails/go/root/golang/go/src/go.mod"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build792114039=/tmp/go-build -gno-record-gcc-switches"

What did you do?

./run.bash -no-rebuild -run=^go_test:runtime

What did you expect to see?

All tests pass

What did you see instead?

--- FAIL: TestFreeBSDNumCPU (0.01s)
    numcpu_freebsd_test.go:13: expected "OK\n", but got:
        runtime.NumCPU() expected to 25, got 24 when run with CPU list 0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23 []string{"0", "1", "2", "3", "4", "5", "6", "7", "8", "9", "10", "11", "12", "13", "14", "15", "16", "17", "18", "19", "20", "21", "22", "23\npid 42890 domain policy: first-touch mask: 0", "1"}
FAIL
FAIL    runtime 10.246s

Clear from the above its a test bug as I have 24 cores not 25.
@stevenh
Copy link
Contributor Author

stevenh commented May 7, 2020

This was previously raised here: #25924

@gopherbot
Copy link

Change https://golang.org/cl/232801 mentions this issue: runtime: Fix TestFreeBSDNumCPU

@ALTree ALTree added the NeedsFix The path to resolution is known, but the work has not been done. label May 8, 2020
@ALTree ALTree added this to the Go1.15 milestone May 8, 2020
@golang golang locked and limited conversation to collaborators May 8, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
FrozenDueToAge NeedsFix The path to resolution is known, but the work has not been done.
Projects
None yet
Milestone
Go1.15
Development

No branches or pull requests
3 participants
@stevenh @ALTree @gopherbot