Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

[test] Verify native child cleanup after interrupted end-to-end suites

Aperta
  • Qualcosa non va?
#166 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
35/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
typescript
Ambito
testing

Direzione di ricerca

Start with docs/specs/20260529-test_strategy.md for the owning cleanup requirements, then docs/verification-instruments.md for the verification method. Reproduce success, test failure and runner cancellation in the Web/Core end-to-end harness and check for fixture-owned child processes afterwards. Done means no owned descendants remain in each case, cleanup targets only positively identified processes, and a repeated run starts clean and reports any cleanup failure.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

enhancement

Summary

Verify native child cleanup after interrupted end-to-end suites.

Category

test or CI

Area

Web and Core end-to-end harness process ownership

Observed behavior and evidence

The acceptance ledger records orphaned test processes and resource pressure during Web/Core end-to-end work. Later positive-PID cleanup guards prevent invalid kill targets, but do not independently prove that every interrupted suite leaves no child processes. Current recurrence remains unverified. Source audit baseline: main 3a54ea25.

Impact

Severity: important. No new release waiver or implementation authorization is implied.

Suggested improvement

Reproduce cancellation/failure at existing harness lifecycle boundaries and inspect only the fixture-owned process tree. Repair demonstrated cleanup gaps with bounded termination and absence proof; keep unrelated processes untouched. Owning specification: docs/specs/20260529-test_strategy.md.

Acceptance criteria

  • Success, test failure and runner cancellation leave no owned fixture descendants.
  • Cleanup uses positively identified processes and cannot target unrelated work.
  • A repeated run starts from clean owned state and reports cleanup failures explicitly.

References

  • docs/specs/20260529-test_strategy.md
  • docs/verification-instruments.md
  • Related: #139

Filed from the v0.1.0 acceptance-program inventory.

Lingua principale
TypeScript
Stelle
0
Fork
0
Merge medio
3h 38m
PR unite (30g)
52

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di lingkaix/openkit

Tutte le issue di lingkaix/openkit

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.