-
Notifications
You must be signed in to change notification settings - Fork 166
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
chore: Upgrade test runner plugins #15102
Conversation
Downgraded surefire to check latest changes specially one bothers me:
|
Try to grab dump files generated by surefire/failsafe to see if there is more information |
The dumpstream file contains
The only thing that stands out in the thread dump is that there are two instances of Files here https://github.com/vaadin/flow/suites/9449041828/artifacts/447046345 |
This is to potentially resolve VM crashes when running tests with Java 19
ab1a64a
to
da10330
Compare
Now the unit tests pass for some reason. Nothing has been fixed but some tests have been removed... But the "slow tests" build fails and that can be reproduced locally as
which results in a similar dumpstream file
and a not very meaningful dump file
I wonder how anybody is even supposed to debug this. Isn't the stdin/stdout stream used internally by surefire an... internal... thing that we cannot affect? |
I deleted all tests but one in The log when it reproduces looks like
but the corruption can also happen much later on
|
When it works, it just runs through all tests
|
TC Format Checker Report - 14:47 - 25 - NovThere are 1 files with format errors
Here is the list of files with format issues in your PR:
|
So this seems to happen almost always when I have a test case that just runs
and nothing else. It does not reproduce if I just run some node command like |
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
This is potentially caused by nodejs/node#42826 as Node seems to change the stdin filedescriptor to non-blocking in some cases. If this happens when running |
Let's close this until the issue has a solution |
This is to potentially resolve VM crashes when running tests with Java 19