Restore the bound-runner regression test in the full-suite baseline

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

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
Da chiarire
Stato di attività
Attiva
Stack tecnologico
aws, python
Ambito
testing

Direzione di ricerca

The failing test test_bound_runner_holds_reviewed_inodes_and_preserves_aws_venv_argv0 is part of the DTC full-suite baseline at revision 35a023da73e9f61173f82e273eea8c001b11830c. Reproduce run 40108254447 job 120914357212 to capture a sanitized traceback. Investigate via the DTC workflow preserving security behavior; done means the test passes in the baseline.

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

Descrizione

bug needs grooming P1 testing

Observed failure

The DTC full-suite baseline reports ERROR for:

test_bound_runner_holds_reviewed_inodes_and_preserves_aws_venv_argv0

This was observed at site revision
35a023da73e9f61173f82e273eea8c001b11830c during the package P16 comparison
in run 40108254447, DTC job 120914357212.

Both the site's pinned-package run and the changed-package run selected
4392 tests and reported this same error. The changed-package run also had
the two documented P16 local-link seal artifacts; its comparison verdict
found no new package failures. The green comparison does not establish a
green DTC baseline.

Diagnosis still needed

The sanitized comparison extraction retained test names and counts only.
The exception type, traceback, and underlying cause are not yet known.
This issue records a baseline defect for investigation, without attributing
it to the released Relay recipient-option change or assuming a timeout or
environment mismatch.

Duplicate check

Searches across open and closed issues for the exact test name, argv0,
and reviewed-inode/bound-runner terms found no exact tracker. Issue 319
names different synthetic runner and container smoke tests; it is not
confirmed to cover this error. Issue 199 concerns component execution
bounds and is closed.

Please obtain a bounded, sanitized traceback and investigate through the
DTC issue workflow while preserving the security behavior this regression
test protects.

Lingua principale
Python
Stelle
0
Fork
0
Merge medio
1m
PR unite (30g)
2

Preparare l'ambiente

  • Include un Dockerfile o un file Docker Compose
  • Nessun modello di pull request
  • Nessuna guida per i contributori

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 DataTalksClub/website

Tutte le issue di DataTalksClub/website

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.