Automattic / Automattic/wp-codebox
Do not fail successful browser probes when browser close exceeds cleanup timeout
- Lingua principale
- TypeScript
- Stelle
- 16
- Fork
- 4
- Merge medio
- 59m
- PR unite (30g)
- 131
Descrizione
## Problem
`wordpress.editor-open` and `wordpress.editor-validate-blocks` can complete navigation, readiness, and artifact capture successfully, then report the whole recipe step as failed because browser cleanup exceeds the fixed 1000ms close timeout. A seven-surface fixture run recorded four `runtime_execution_failed` findings solely from `operation=browser-close-timeout`.
## Evidence
- Homeboy run: `b280bf88-2257-4915-9d80-f4c52ff6a538`
- WP Codebox: `0.18.4`
- Browser: HeadlessChrome `151.0.7922.34`
- Fixture: `37-art-gallery-exhibition`
- Affected steps: editor-open and editor-validate-blocks
- Captured summaries show navigation/readiness succeeded and artifacts were written before close cleanup timed out.
Reproduction:
```sh
node tools/run-fixture-matrix.mjs --static-site-importer /path/to/static-site-importer --blocks-engine /path/to/blocks-engine --local --target-fixture 37-art-gallery-exhibition --surface-coverage 6
```
## Acceptance
- Browser close cleanup has a realistic bounded timeout or terminates the browser process deterministically.
- A cleanup timeout retains diagnostics without converting an otherwise successful probe and its valid artifacts into a workload failure.
- Repeated multi-surface editor-open and editor-validate-blocks runs complete without close-timeout findings.
## AI Assistance
OpenAI GPT-5.6 Sol via OpenCode ran the seven-surface matrix, inspected retained editor artifacts, and drafted this report. Chris Huber reviewed the evidence and remains responsible for the issue.
Guida per i contributori
Nessuna guida per i contributori indicizzata per questo repository
Direzione di ricerca
Esegui tools/run-fixture-matrix.mjs con il fixture di destinazione e rendi visibile la copertura della riproduzione, quindi traccia la pulizia per le probe wordpress.editor-open e wordpress.editor-validate-blocks. Il lavoro è completato quando la pulizia rimane circoscritta o deterministica, i diagnostici vengono mantenuti, le probe riuscite non diventano fallimenti e le esecuzioni ripetute su più superfici non presentano rilevamenti browser-close-timeout.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- node.js, typescript
- Ambito
- testing-qa
- Tipo di issue
- Bug
- Difficoltà
- 3/5
- Tempo stimato
- 1-2 giorni
- Stato di attività
- Tranquilla
- Chiarezza
- Abbastanza chiara
- Idoneità per principianti
- 58/100