-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
WebKitGTK experimental runs missing since August 13 #47823
Comments
The problem has been caused because an upgrade on the toolchain on the server generating the webkitgtk built-products also upgraded the libstdc++ version on the container and therefore the built-products generated are now incompatible with Ubuntu-20.04 Building webkitgtk requires gcc >= 11 nowadays and that is an issue as it is becoming increasingly hard to keep providing build-products for such old distro. I think we should look into upgrading the docker container that is used for the WPT CI tests at taskcluster. Related: #43361 |
We are going to start providing a generic bundle that can work on any distro and has all the bleeding edge features enabled instead of providing a bundle with several features disabled to make it compile on an ancient distro like Ubuntu-20.04 I will submit a patch here to switch the WPT tooling to pull this new bundle once ready and that should make the webkitgtk runs work back as expected. Work for shipping the new bundle tracked at https://bugs.webkit.org/show_bug.cgi?id=280523 and the bugs linked there in see-also |
The runs on the CI (TaskCluster) of WebKitGTK have been not working since a while [1] because the nightly bundles that we were shipping for download [2] for testing on the WPT CI stopped working due to binary compatibility issues. So we decided [3] that instead of shipping a bundle for a specific distro we would ship an universal bundle that can work on any distro. This allows us to ship a bundle with all the preview features enabled and the last versions of all the libraries, matching the same configurations that are tested on the release WebKitGTK bots at build.webkit.org This commit changes the taskcluster init tasks, as also the installation of the webkitgtk_minibrowser bundles to use this new universal bundle. This also allows now developers to test with webkitgtk_minibrowser nightlies independent of the distro they have. They simply need to pass the flags "--install-browser --channel=nightly" to "wpt run" [1] Fixes: web-platform-tests#47823 [2] https://webkitgtk.org/built-products/x86_64/release/nightly [3] https://bugs.webkit.org/show_bug.cgi?id=280523
Ok, the new bundles are ready to be used and I submitted at #48698 the changes so the WPT taskcluster CI system start using them |
The runs on the CI (TaskCluster) of WebKitGTK have been not working since a while [1] because the nightly bundles that we were shipping for download [2] for testing on the WPT CI stopped working due to binary compatibility issues. So we decided [3] that instead of shipping a bundle for a specific distro we would ship an universal bundle that can work on any distro. This allows us to ship a bundle with all the preview features enabled and the last versions of all the libraries, matching the same configurations that are tested on the release WebKitGTK bots at build.webkit.org This commit changes the taskcluster init tasks, as also the installation of the webkitgtk_minibrowser bundles to use this new universal bundle. This also allows now developers to test with webkitgtk_minibrowser nightlies independent of the distro they have. They simply need to pass the flags "--install-browser --channel=nightly" to "wpt run" [1] Fixes: web-platform-tests#47823 [2] https://webkitgtk.org/built-products/x86_64/release/nightly [3] https://bugs.webkit.org/show_bug.cgi?id=280523
The last run for WebKitGTK Experimental was August 13
https://wpt.fyi/runs?label=master&label=experimental&max-count=100&product=chrome&product=edge&product=firefox&product=safari&product=webkitgtk
@clopez could you take a look please?
The text was updated successfully, but these errors were encountered: