Skip to content
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

Merged
merged 1 commit into from
Feb 1, 2020
Merged

Kill off hanging crashtests. #25670

merged 1 commit into from
Feb 1, 2020

Conversation

jdm
Copy link
Member

@jdm jdm commented Feb 1, 2020

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

@highfive highfive added the S-awaiting-review There is new code that needs to be reviewed. label Feb 1, 2020
@servo-wpt-sync
Copy link
Collaborator

Opened new PR for upstreamable changes.

Completed upstream sync of web-platform-test changes at web-platform-tests/wpt#21537.

@jdm
Copy link
Member Author

jdm commented Feb 1, 2020

@bors-servo p=3 r+

@bors-servo
Copy link
Contributor

📌 Commit 44a2953 has been approved by jdm

@highfive highfive added S-awaiting-merge The PR is in the process of compiling and running tests on the automated CI. and removed S-awaiting-review There is new code that needs to be reviewed. labels Feb 1, 2020
@highfive highfive assigned jdm and unassigned asajeffrey Feb 1, 2020
@bors-servo
Copy link
Contributor

⌛ Testing commit 44a2953 with merge d034882...

bors-servo pushed a commit that referenced this pull request Feb 1, 2020
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
@bors-servo
Copy link
Contributor

💔 Test failed - status-taskcluster

@highfive highfive added S-tests-failed The changes caused existing tests to fail. and removed S-awaiting-merge The PR is in the process of compiling and running tests on the automated CI. labels Feb 1, 2020
@bors-servo
Copy link
Contributor

⌛ Testing commit 44a2953 with merge 85f1096...

bors-servo pushed a commit that referenced this pull request Feb 1, 2020
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
@highfive highfive added S-awaiting-merge The PR is in the process of compiling and running tests on the automated CI. and removed S-tests-failed The changes caused existing tests to fail. labels Feb 1, 2020
@bors-servo
Copy link
Contributor

💔 Test failed - status-taskcluster

@highfive highfive added S-tests-failed The changes caused existing tests to fail. and removed S-awaiting-merge The PR is in the process of compiling and running tests on the automated CI. labels Feb 1, 2020
@bors-servo
Copy link
Contributor

⌛ Testing commit 44a2953 with merge 0f4066a...

bors-servo pushed a commit that referenced this pull request Feb 1, 2020
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
@highfive highfive removed the S-tests-failed The changes caused existing tests to fail. label Feb 1, 2020
@highfive highfive added the S-awaiting-merge The PR is in the process of compiling and running tests on the automated CI. label Feb 1, 2020
@bors-servo
Copy link
Contributor

☀️ Test successful - status-taskcluster
Approved by: jdm
Pushing 0f4066a to master...

@bors-servo bors-servo merged commit 44a2953 into servo:master Feb 1, 2020
@highfive highfive removed the S-awaiting-merge The PR is in the process of compiling and running tests on the automated CI. label Feb 1, 2020
@servo-wpt-sync
Copy link
Collaborator

Error syncing changes upstream. Logs saved in error-snapshot-1580533360933.

@CYBAI
Copy link
Member

CYBAI commented Feb 1, 2020

@jdm not sure what error it is; I saw the do not merge yet label was removed from web-platform-tests/wpt#21537 but it's not merged 🤔 We might need to merge that manually?

@CYBAI
Copy link
Member

CYBAI commented Feb 25, 2020

#25796 (comment) reminds me to check this one and it's not merged yet 👀 cc @jdm

@jdm
Copy link
Member Author

jdm commented Feb 25, 2020

Thanks for the reminder! I manually merged it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants