-
Notifications
You must be signed in to change notification settings - Fork 36
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
cockpit-ci: Update container to 2025-01-18 #911
cockpit-ci: Update container to 2025-01-18 #911
Conversation
770c197
to
bfcad0e
Compare
Urgh, what? that's hopefully not a browser regression. Running again to compare. If that is true, we have a major bug. |
second run has one case fixed, but the disappearing "Change" button is persistent. On to the pilot board. |
This effortlessly reproduces locally (fortunately I already have that new container locally, so train material).
So in summary, this is a chromium headless bug. |
This is the second headless bug after cockpit-project/cockpit@0ec830d that I remember. Replacing chromium-headless with chromium in our tasks container will result in a net 100 MB increase, but avoid these two bugs, and also provide us with a reproducible So I propose to change our tasks container accordingly, suffer through the mass pixel change once, but from then on our lives will be a bit easier. @jelly WDYT? |
The headless version has several bugs, at least [1] and [2]. Also, headless and full Chromium render texts slightly differently, so we can't debug/fix pixel tests with `TEST_SHOW_BROWSER=pixels`. This is a net 100 MB size increase of the tasks container, and will break all pixel tests once, but long-term it is a better browser. [1] https://issues.redhat.com/browse/COCKPIT-1159 [2] cockpit-project/cockpit-files#911 (comment)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's not do this, and instead do cockpit-project/cockpituous#637
The headless version has several bugs, at least [1] and [2]. Also, headless and full Chromium render texts slightly differently, so we can't debug/fix pixel tests with `TEST_SHOW_BROWSER=pixels`. This is a net 100 MB size increase of the tasks container, and will break all pixel tests once, but long-term it is a better browser. [1] https://issues.redhat.com/browse/COCKPIT-1159 [2] cockpit-project/cockpit-files#911 (comment)
No description provided.