-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
Kill off hanging crashtests. #25670
Kill off hanging crashtests. #25670
Conversation
Opened new PR for upstreamable changes. Completed upstream sync of web-platform-test changes at web-platform-tests/wpt#21537. |
@bors-servo p=3 r+ |
📌 Commit 44a2953 has been approved by |
Kill off hanging crashtests. The reason that complex-glsl-does-not-crash.html kept leaving zombie processes is the following: * WPT introduced the notion of crash tests (ie. tests that verify that they do not crash) * if a timeout expires while running a crash test and the test has not finished running, it is reported as a failure and potential hang * there is no code that causes a hanging test to stop running * any test filename that ends in `-crash` is automatically treated as a crashtest
💔 Test failed - status-taskcluster |
Kill off hanging crashtests. The reason that complex-glsl-does-not-crash.html kept leaving zombie processes is the following: * WPT introduced the notion of crash tests (ie. tests that verify that they do not crash) * if a timeout expires while running a crash test and the test has not finished running, it is reported as a failure and potential hang * there is no code that causes a hanging test to stop running * any test filename that ends in `-crash` is automatically treated as a crashtest
💔 Test failed - status-taskcluster |
Kill off hanging crashtests. The reason that complex-glsl-does-not-crash.html kept leaving zombie processes is the following: * WPT introduced the notion of crash tests (ie. tests that verify that they do not crash) * if a timeout expires while running a crash test and the test has not finished running, it is reported as a failure and potential hang * there is no code that causes a hanging test to stop running * any test filename that ends in `-crash` is automatically treated as a crashtest
☀️ Test successful - status-taskcluster |
Error syncing changes upstream. Logs saved in error-snapshot-1580533360933. |
@jdm not sure what error it is; I saw the |
#25796 (comment) reminds me to check this one and it's not merged yet 👀 cc @jdm |
Thanks for the reminder! I manually merged it. |
The reason that complex-glsl-does-not-crash.html kept leaving zombie processes is the following:
-crash
is automatically treated as a crashtest