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
Missing WebKitGTK runs since June 22 #24360
Comments
This is the same as #24257:
|
Yes.. same issue. We need to avoid failing the taskcluster CI run if the browser doesn't support the print-reftest tests (or skip those tests) |
To keep things synced - it seems like nobody currently owns #24257, so if there's a desire to get WebKitGTK back on wpt.fyi someone needs to step up and add 'skip if not supported' logic or something similar to that. |
Thanks for the heads up. There is definitively a desire to get WebKitGTK back on wpt.fyi. I have a patch that I think it can work. .. will upload the PR now |
* print-reftests are currently not supported for this two browsers. So we need to avoid triggering those runs on taskcluster for them to avoid failing the whole run. This fixes: web-platform-tests#24360 and web-platform-tests#24257. * This patch removes the print-reftest suite from the general block and adds a new block for it and for the browsers that support this tests on taskcluster (chrome and firefox).
…#24576) * print-reftests are currently not supported for this two browsers. So we need to avoid triggering those runs on taskcluster for them to avoid failing the whole run. This fixes: web-platform-tests#24360 and web-platform-tests#24257. * This patch removes the print-reftest suite from the general block and adds a new block for it and for the browsers that support this tests on taskcluster (Chrome and Firefox).
* print-reftests are currently not supported for this two browsers. So we need to avoid triggering those runs on taskcluster for them to avoid failing the whole run. This fixes: #24360 and #24257. * This patch removes the print-reftest suite from the general block and adds a new block for it and for the browsers that support this tests on taskcluster (Chrome and Firefox).
As per https://wpt.fyi/runs?label=master&label=experimental&max-count=100&product=chrome&product=edge&product=firefox&product=safari&product=webkitgtk the last successful WebKitGTK run was June 22 (4 days ago).
Any idea what's going on?
The text was updated successfully, but these errors were encountered: