runtime: TestGcSys is still flaky

Repository metrics

Stars

133,883 stars (133,883 stars)

PR merge metrics

No merged PRs in 30d (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

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