golang/go

runtime: TestGcSys is still flaky

Open

#37,331 opened on Feb 20, 2020

View on GitHub
 (47 comments) (1 reaction) (1 assignee)Go (19,008 forks)batch import
NeedsInvestigationhelp wanted

Repository metrics

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

Description

--- FAIL: TestGcSys (0.03s)
    gc_test.go:27: expected "OK\n", but got "using too much memory: 70486024 bytes\n"
FAIL
FAIL	runtime	50.446s

See previously #28574, #27636, #27156, #23343.

CC @mknyszek @aclements

2020-02-15T16:40:12-6917529/freebsd-amd64-race 2020-02-05T18:27:48-702226f/freebsd-amd64-race 2020-01-31T15:04:07-f2a4ab3/freebsd-amd64-race 2020-01-07T19:53:19-7d98da8/darwin-amd64-10_15 2019-12-31T12:11:24-bbd25d2/solaris-amd64-oraclerel 2019-12-11T00:01:17-9c8c27a/solaris-amd64-oraclerel 2019-11-04T15:18:34-d3660e8/plan9-386-0intro 2019-09-12T14:08:16-3d522b1/solaris-amd64-smartosbuildlet

Contributor guide

Research direction
Investigate the flaky TestGcSys test: trace the memory usage checks to understand why it sometimes exceeds the expected limit. Look for race conditions or timing issues in the GC cycle.
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.
3
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.
Clear
Prerequisites
GoGarbage Collection
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30