Skip to content

GFQL: residual benchmark triage/split tooling for #880#1330

Closed
lmeyerov wants to merge 4 commits intomasterfrom
issue-880-benchmark-row-bindings
Closed

GFQL: residual benchmark triage/split tooling for #880#1330
lmeyerov wants to merge 4 commits intomasterfrom
issue-880-benchmark-row-bindings

Conversation

@lmeyerov
Copy link
Copy Markdown
Contributor

@lmeyerov lmeyerov commented May 7, 2026

Summary

Implements issue #880 triage/split tooling by adding a reproducible parser/reporter for benchmark residual lanes still tagged to graphistry/pygraphistry#880.

What this adds

  • New typed module: graphistry.compute.gfql.benchmark_residual_triage
    • Loads pyg-bench run artifacts (probe-results.json, optional run-manifest.json, optional remote-execution.json)
    • Filters residual lanes by issue ref (backend=gfql, status=partial)
    • Selects latest run per lane
    • Buckets residuals by root-cause heuristic
    • Renders split-ready markdown child-issue drafts with concrete repro evidence
  • CLI wrapper: bin/gfql_issue_880_triage.py
  • Tests: graphistry/tests/compute/gfql/test_benchmark_residual_triage.py
  • Doc pointer: ai/docs/gfql/README.md

Why

#880 remains an umbrella with multiple benchmark-visible residuals. This PR provides a concrete, repeatable way to convert raw benchmark artifacts into narrow child issue drafts with reproducible evidence.

Validation

  • ./bin/ruff.sh graphistry/compute/gfql/benchmark_residual_triage.py graphistry/tests/compute/gfql/test_benchmark_residual_triage.py bin/gfql_issue_880_triage.py
  • ./bin/mypy.sh graphistry/compute/gfql/benchmark_residual_triage.py graphistry/tests/compute/gfql/test_benchmark_residual_triage.py bin/gfql_issue_880_triage.py
  • python3 -m pytest -q graphistry/tests/compute/gfql/test_benchmark_residual_triage.py
  • python3 bin/gfql_issue_880_triage.py --runs-dir /home/lmeyerov/Work/pyg-bench/results/runs --output /tmp/issue-880-residual-triage.md

Example usage

python bin/gfql_issue_880_triage.py --runs-dir ../pyg-bench/results/runs --output /tmp/issue-880-residual-triage.md

@lmeyerov
Copy link
Copy Markdown
Contributor Author

lmeyerov commented May 7, 2026

Closing as intentionally empty after full revert (changedFiles=0, additions=0, deletions=0).

Coordinator decision: benchmark-residual triage logic for #880 should live in pyg-bench/private planning artifacts, not shipping pygraphistry runtime code.

Follow-up remains tracked in #880 via benchmark evidence/repros and scoped child issues where needed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant