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

runtime: TestMemoryLimitNoGCPercent failures #66893

Closed
gopherbot opened this issue Apr 18, 2024 · 3 comments
Closed

runtime: TestMemoryLimitNoGCPercent failures #66893

gopherbot opened this issue Apr 18, 2024 · 3 comments
Assignees
Labels
compiler/runtime Issues related to the Go compiler and/or runtime. NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided.
Milestone

Comments

@gopherbot
Copy link
Contributor

#!watchflakes
default <- pkg == "runtime" && test == "TestMemoryLimitNoGCPercent"

Issue created automatically to collect these failures.

Example (log):

=== RUN   TestMemoryLimitNoGCPercent
    gc_test.go:938: /Users/swarming/.swarming/w/ir/x/t/go-build147963065/testprog.exe GCMemoryLimitNoGCPercent: exit status 2
    gc_test.go:941: expected "OK\n", but got "retained=285218056 limit=268435456 bound=285212672\npanic: exceeded memory limit by more than bound allows\n\ngoroutine 1 [running]:\nmain.gcMemoryLimit(0xffffffffffffffff)\n\t/Users/swarming/.swarming/w/ir/x/w/goroot/src/runtime/testdata/testprog/gc.go:404 +0x465\nmain.GCMemoryLimitNoGCPercent()\n\t/Users/swarming/.swarming/w/ir/x/w/goroot/src/runtime/testdata/testprog/gc.go:317 +0x1a\nmain.main()\n\t/Users/swarming/.swarming/w/ir/x/w/goroot/src/runtime/testdata/testprog/main.go:34 +0x133\n"
--- FAIL: TestMemoryLimitNoGCPercent (2.46s)

watchflakes

@gopherbot gopherbot added the NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. label Apr 18, 2024
@gopherbot gopherbot added the compiler/runtime Issues related to the Go compiler and/or runtime. label Apr 18, 2024
@gopherbot
Copy link
Contributor Author

Found new dashboard test flakes for:

#!watchflakes
default <- pkg == "runtime" && test == "TestMemoryLimitNoGCPercent"
2024-03-27 17:55 gotip-darwin-amd64-longtest go@a16b4bf3 runtime.TestMemoryLimitNoGCPercent (log)
=== RUN   TestMemoryLimitNoGCPercent
    gc_test.go:938: /Users/swarming/.swarming/w/ir/x/t/go-build147963065/testprog.exe GCMemoryLimitNoGCPercent: exit status 2
    gc_test.go:941: expected "OK\n", but got "retained=285218056 limit=268435456 bound=285212672\npanic: exceeded memory limit by more than bound allows\n\ngoroutine 1 [running]:\nmain.gcMemoryLimit(0xffffffffffffffff)\n\t/Users/swarming/.swarming/w/ir/x/w/goroot/src/runtime/testdata/testprog/gc.go:404 +0x465\nmain.GCMemoryLimitNoGCPercent()\n\t/Users/swarming/.swarming/w/ir/x/w/goroot/src/runtime/testdata/testprog/gc.go:317 +0x1a\nmain.main()\n\t/Users/swarming/.swarming/w/ir/x/w/goroot/src/runtime/testdata/testprog/main.go:34 +0x133\n"
--- FAIL: TestMemoryLimitNoGCPercent (2.46s)

watchflakes

@mknyszek mknyszek self-assigned this Apr 24, 2024
@mknyszek mknyszek added this to the Backlog milestone May 8, 2024
@mknyszek
Copy link
Contributor

This is a possible fluke of the test, so I'm not going to ascribe any real issues to it unless we start seeing it occur more regularly.

@mknyszek mknyszek added the WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided. label Nov 26, 2024
@gopherbot
Copy link
Contributor Author

Timed out in state WaitingForInfo. Closing.

(I am just a bot, though. Please speak up if this is a mistake or you have the requested information.)

@gopherbot gopherbot closed this as not planned Won't fix, can't repro, duplicate, stale Dec 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
compiler/runtime Issues related to the Go compiler and/or runtime. NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided.
Projects
Status: Done
Development

No branches or pull requests

2 participants