Shenandoah Support

[dwragge]

Hi guys,

I see that Shenandoah has been mostly stubbed out and nothing is really parsed. Do we have plans to support Shenandoah?

Cheers,
Dylan

[dsgrieve]

Given the choice between adding support for Shenandoah and ZGC, we chose ZGC. There just weren't enough resources to tackle both.

[karianna]

Dylan Wragge (@dwragge) - Contributions are of course always welcome :-)

[brunoborges]

/relevance-check

[github-actions]

Relevance Assessment: Still Relevant

• Summary: Shenandoah GC log parsing remains fully stubbed out in the codebase. The issue's observation is still accurate — no functional Shenandoah support has been implemented since this issue was opened.

• Evidence:

  • ShenandoahParser.java (lines 40–43) only registers the END_OF_FILE parse rule — none of the 26 patterns defined in ShenandoahPatterns.java are wired up.
  • ShenandoahForwardReference.toShenandoahCycle() returns null (line 112–114), meaning no events are ever produced.
  • ShenandoahParserTest.java has its test disabled with the comment //todo: support for Shenandoah still under construction.
  • There is only 1 event class (ShenandoahCycle.java) compared to ZGC's 23 fully-implemented event classes.
  • No commits mentioning "Shenandoah" exist in the git history, and no PRs have been opened to implement Shenandoah parsing.
  • The scaffolding is in place (patterns, event class, test files), but the core parsing logic connecting patterns to events is entirely missing.
  • A maintainer confirmed in the original comment that ZGC was prioritized over Shenandoah due to resource constraints.

• Recommendation: ✅ Keep open — Shenandoah support is a valid feature gap. The scaffolding exists (patterns, event class, test data), which could help a contributor pick this up. This issue serves as a useful tracker for the feature request and a pointer for potential contributors.

Generated by Relevance Check Agent for issue #443