Skip to content

GraalPy: collect_until's late-finaliser test outruns its 5 s grace #2016

Closed

Description

@JarryShaw

Describe the bug
On GraalPy, FinaliserBackstopWithoutDel.test_collect_until_waits_out_a_finaliser_that_runs_late in tests/foundation/test_extraction_ownership.py fails: collect_until(late, grace=5.0) returns False. The predicate needs three collections, and under the loaded sharded run, GraalPy does not fit three gc.collect calls into the hard-coded 5 s.

Reproduction
The graalpy-25.4 experimental leg on main f96a6b156 (job):

>       self.assertTrue(collect_until(late, grace=5.0))
E       AssertionError: False is not true

Expected behavior
The test should check how collect_until behaves without depending on how fast gc.collect runs on the engine.

System information

  • OS Version: ubuntu-latest (GitHub Actions)
  • Python Implementation: GraalPy 25.4
  • commit: f96a6b156

Additional context
This came out of the #1963 re-measure. collect_until came from #2010.

Activity

  1. added
    bugIssues reporting a defect (set by the bug report template; a default, not an assessment)
    testPull requests that add or correct tests (test: subject prefix)
    wipWork in flight - a covering PR is open or an agent is actively on it
    on Oct 21, 2026
  2. removed
    wipWork in flight - a covering PR is open or an agent is actively on it
    on Oct 23, 2026
  3. added this to the PyPCAPKit v1.5 milestone on Oct 26, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugIssues reporting a defect (set by the bug report template; a default, not an assessment)testPull requests that add or correct tests (test: subject prefix)

    Projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions