Skip to content

Handle noisy wordpress.bench result output#961

Open
chubes4 wants to merge 1 commit into
mainfrom
fix-bench-warning-prefix
Open

Handle noisy wordpress.bench result output#961
chubes4 wants to merge 1 commit into
mainfrom
fix-bench-warning-prefix

Conversation

@chubes4

@chubes4 chubes4 commented Jun 14, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • Recover wp-codebox/bench-results/v1 JSON from successful wordpress.bench stdout when PHP/WordPress warning text is printed before or after the structured envelope.
  • Preserve the non-JSON output as benchResults.diagnostics so warnings remain visible without corrupting recipe-run parsing.
  • Extend recipe-bench-smoke with a fixture workload that emits warning-like HTML before valid bench JSON.

Fixes #959.

Validation

  • npm run build
  • npx tsx scripts/recipe-bench-smoke.ts

AI assistance

  • AI assistance: Yes
  • Tool(s): OpenCode (GPT-5.5)
  • Used for: Investigated the wordpress.bench recipe-run parsing path, drafted the parser fix and targeted smoke coverage, and ran validation commands. Chris remains responsible for review and merge.

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.

wordpress.bench should not let PHP warning output corrupt bench-result JSON

1 participant