-
-
Notifications
You must be signed in to change notification settings - Fork 230
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Random failures of ProgressPrinter #734
Comments
Mmm, I see this can happen, but impossible for me to debug and fix it without a reproducible environment. Can you try to log to a file the content of these 3 variables:
Just after they have been set in |
Yea, unfortunately very hard to reproduce. Of course it hasn't happened again since I opened the issue 🙄 . I'll try to implement the logging you suggested in a fork to do it "passively". My suspicion is that it could be related to data providers, because the So maybe the end of the column is calculated wrong in tests with data provider? And with random order set in phpunit config, it only fails in very few cases when the test is in the "wrong" position in the progress printer. If I have some time in the next few days I'll try to create a reproducer. |
Hi, Here is the output. @Slamdunk I logged those values to the screen you asked for.
|
This is an unrelated error, just fixed in sebastianbergmann/phpunit#5251 (but still unreleased at the time of writing) |
@Slamdunk My bad. Thanks! |
I had some more errors today, all occurred in the same file, so at least theres hope to reproduce it 🤞 |
This issue has gone two months without activity. In another two weeks, I will close it. But! If you comment or otherwise update it, I will reset the clock, and if you label it |
Summary
I get random failures of
ProgressPrinter
, both locally and on CI. They only happen when running the tests with paratest, not phpunit itself, so I'm opening the issue here. Unfortunately I could not reliably reproduce it yet. See output below:PHPUnit config:
The text was updated successfully, but these errors were encountered: