Skip to content

race condition bug or a flaky test: TestAddMultipleGCLive #10487

Closed

Description

@lidel

Not sure if this is a flaky test, or a sign of underlying bug.
We should look into this in spare time.

Confirmed this is pretty old bug, reproduces with v0.23.0 and v0.29.0, and the latest master for 0.30.0-rc1.

Not a big surprise, MFS has always been flaky (#8131),
just documenting here so the next person does not waste time on debugging "new bug".

To reproduce, keep runing TestAddMultipleGCLive many times, it will eventually deadlock on something and produce a timeout:

$ while go test -run TestAddMultipleGCLive -count 100 -timeout 10s ./core/coreunix/...; do sleep 1; done
ok  	github.com/ipfs/kubo/core/coreunix	0.241s
ok  	github.com/ipfs/kubo/core/coreunix	0.339s
ok  	github.com/ipfs/kubo/core/coreunix	0.267s
ok  	github.com/ipfs/kubo/core/coreunix	0.253s
panic: test timed out after 10s
	running tests:
		TestAddMultipleGCLive (10s)
[.. a long stack for panic ..] 

Activity

  1. added
    kind/bugA bug in existing code (including security flaws)
    need/triageNeeds initial labeling and prioritization
    on Aug 21, 2024
  2. self-assigned this
    on Apr 1, 2025
  3. added
    P2Medium: Good to have, but can wait until someone steps up
    on Apr 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

P2Medium: Good to have, but can wait until someone steps upkind/bugA bug in existing code (including security flaws)kind/testTesting worktopic/test failureTopic test failure

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions