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: TestMemStats failure with insanely high value on openbsd-amd64-68 #55065

Open
bcmills opened this issue Sep 14, 2022 · 2 comments
Open

runtime: TestMemStats failure with insanely high value on openbsd-amd64-68 #55065

bcmills opened this issue Sep 14, 2022 · 2 comments
Labels
NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. OS-OpenBSD
Milestone
Backlog

Comments

@bcmills
Copy link
Contributor

bcmills commented Sep 14, 2022 •
edited by rsc 

#!watchflakes
post <- pkg == "runtime" && test == "TestMemStats" && `insanely high value`

##### GOMAXPROCS=2 runtime -cpu=1,2,4 -quick
--- FAIL: TestMemStats (0.00s)
    malloc_test.go:93: PauseTotalNs = 18446744073177999286: insanely high value (overflow?); want <= 1e+11
FAIL
FAIL	runtime	21.088s

greplogs -l -e 'FAIL: TestMemStats.*(?:\n\s+.*)*insanely high value' --since=2022-01-01
2022-09-09T01:04:57-76c94eb/openbsd-amd64-68

attn @golang/openbsd; CC @golang/runtime
@gopherbot gopherbot added the compiler/runtime Issues related to the Go compiler and/or runtime. label Sep 14, 2022
@bcmills bcmills added this to the Backlog milestone Sep 14, 2022
@bcmills bcmills added NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. and removed compiler/runtime Issues related to the Go compiler and/or runtime. labels Sep 14, 2022
@mknyszek
Copy link
Contributor

... We should really update that error message.

I'm going to guess this is a product of the fact that OpenBSD has coarse-grained timers. As the error message suggests, this looks to me like a negative duration (note PauseTotalNs is a uint64, so the int64 nanotime result is cast first).

I guess the fix is to defensively check for a negative duration and clamp at zero?

This was referenced Sep 14, 2022
Closed
Closed
@gopherbot
Copy link

Found new matching dashboard test flakes for:

#!watchflakes
post <- pkg == "runtime" && test == "TestMemStats" && `insanely high value`
2022-09-09 01:04 openbsd-amd64-68 go@76c94eb7 runtime.TestMemStats (log) 
--- FAIL: TestMemStats (0.00s)
    malloc_test.go:93: PauseTotalNs = 18446744073177999286: insanely high value (overflow?); want <= 1e+11

— watchflakes

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. OS-OpenBSD
Projects
Test Flakes
Status: Active
Milestone
Backlog
Development

No branches or pull requests
3 participants
@mknyszek @bcmills @gopherbot