[Bug]: In TIA mode on Windows there's a 1 minute execution overhead, even 100% of tests are replayed and Pest reports "just 2 seconds"

Aperta
#1,880 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 5 giorni

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
48/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Tranquilla
Stack tecnologico
git, php

Direzione di ricerca

Start by reproducing pest --parallel --tia on Windows after changing many test files, comparing Pest’s Duration with wall-clock time. Investigate the TIA change-detection path and the suspected repeated git show calls, then verify that the reported duration tracks actual execution time when most results are replayed.

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

Descrizione

bug
What Happened

Pest reporting about execution time in TIA mode when many files are changed, but none actually should invoke real test iteration just a replay- do not match actual real execution time (say reported by time command). Action goes on Windows.

How to Reproduce
  1. On Windows OS, change 100 test files slightly with no actual influential changes (like add spaces, comments etc).
  2. Run pest --parallel --tia
  3. Observe 20x-50x times execution penalty, i.e. What Pest reports in "Duration" column and how much Pest process execution actually took (reported with time utility or by other means)

Expected results:
Real execution time should match the one Pest reports. So there's a probable execution overhead on windows when many files are changed, but very tiny amount of them (or none at all) actually leads to a test execution, i,.e. TIA replays most of results.

Sample Repository

No response

Pest Version

5.1.1

PHP Version

8.4.19

Operation System

Windows

Notes

Suggested resolution. I am suspecting that most overhead in windows comes from making many calls to "git show" or similar git commands which fetches actual changes file-by-file. If so, scanning could be done by streaming changes of many objects in one go with git cat-file --batch or similar.

Lingua principale
PHP
Stelle
11.8k
Fork
559
Merge medio
5g 23h
PR unite (30g)
24

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 pestphp/pest

Tutte le issue di pestphp/pest

Issue simili

Altre issue su PHP

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.