Permanent Windows browser_parsable_css.js | Got error message for autocomplete-item.css: Expected color but found �color-mix�. Error in parsing value for �background-color�. Declaration dropped. - when Gecko 94 merges to Beta on 2021-10-04
Categories
(Toolkit :: Form Autofill, defect, P1)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr78 | --- | unaffected |
firefox-esr91 | --- | unaffected |
firefox92 | --- | unaffected |
firefox93 | --- | unaffected |
firefox94 | + | fixed |
firefox95 | --- | verified |
People
(Reporter: aryx, Assigned: tgiles)
References
(Regression)
Details
(Keywords: regression)
Attachments
(2 files)
TEST-UNEXPECTED-FAIL | browser/base/content/test/static/browser_parsable_css.js | Got error message for jar:file:///Z:/task_1633008422/build/application/firefox/browser/features/formautofill@mozilla.org.xpi!/chrome/content/skin/autocomplete-item.css: Expected color but found color-mix. Error in parsing value for background-color. Declaration dropped. -
TEST-UNEXPECTED-FAIL | browser/base/content/test/static/browser_parsable_css.js | All the styles (239) loaded without errors. - Got 1, expected +0
Assignee | ||
Comment 1•3 years ago
|
||
Hey :aryx, this is the first time I've encountered a situation like this. Do I just follow the instructions in "TRUNK AS EARLY BETA", i.e. make my fix and then test against the simulation by running ./mach try release -v 94.0b1 --tasks release-sim --migration central-to-beta
? Or do I need to get access and open the simulation doc based on the instructions under "Beta Simulations"? Sorry for the dumb questions, but I'm a bit lost.
Reporter | ||
Comment 2•3 years ago
|
||
Please run
./mach try release -v 94.0b1 --tasks release-sim --migration central-to-beta --no-push
hg commit -m "Early Beta config"
./mach try chooser --full --artifact browser/base/content
or similar.
In the end, color-mix
cannot be used because it's only enabled on Nightly.
Assignee | ||
Comment 3•3 years ago
|
||
I'll add a workaround for this, but I also need to determine where this stylesheet is being loaded from since it should be a resource/chrome stylesheet and have access to color-mix
.
Assignee | ||
Comment 4•3 years ago
|
||
After setting up the early beta config, I went through Try chooser but it looks like the tree is closed right now
remote: ************************** ERROR ****************************
remote: Error accessing https://treestatus.mozilla-releng.net/trees/try :
remote: <urlopen error EOF occurred in violation of protocol (_ssl.c:877)>
remote: Unable to check if the tree is open - treating as if CLOSED.
remote: To push regardless, include "CLOSED TREE" in your push comment.
remote: *************************************************************
remote:
remote:
remote: transaction abort!
remote: rollback completed
To hg::ssh://hg.mozilla.org/try
! [remote rejected] HEAD -> branches/default/tip (nothing changed on remote)
error: failed to push some refs to 'hg::ssh://hg.mozilla.org/try'
I'll try again tomorrow and see what happens.
Assignee | ||
Updated•3 years ago
|
Updated•3 years ago
|
Assignee | ||
Comment 5•3 years ago
|
||
Updated•3 years ago
|
Updated•3 years ago
|
Updated•3 years ago
|
Reporter | ||
Comment 6•3 years ago
|
||
Dimi, the test fixed the reported the issue. Can you get it reviewed and landed?
Comment 7•3 years ago
•
|
||
(In reply to Sebastian Hengst [:aryx] (needinfo on intermittent or backout) from comment #6)
Dimi, the test fixed the reported the issue. Can you get it reviewed and landed?
ah, sorry for the late reply, I missed the needinfo somehow.
I'm not sure what the current status of this patch is, so not sure what the next step is to proceed.
I think :tim had discussed with :sfoster before taking PTO. I'll redirect the needinfo to sam because I believe sam has more context on this bug.
Comment 8•3 years ago
|
||
Thanks Dimi,
I can commandeer the revision and get this landed.
:aryx, is there a way I can verify this patch locally? I just built beta and ran the test without the patch and it passed. Is there something I need in my mozconfig to ensure I'm testing correctly?
Reporter | ||
Comment 9•3 years ago
|
||
Code sheriffs imported the patch and it resolved the issue.
I never compile a central-as-beta build locally, only 'built' artifact builds for Linux opt. Beta + Windows only builds PGO optimized ("shippable") builds. You can follow the central-as-beta instructions with the mentioned --no-push
, commit the changes and then build. Or do that config change, add the Windows opt build to yesterday's central-as-beta simulation and use that for your artifact build.
Updated•3 years ago
|
Updated•3 years ago
|
Updated•3 years ago
|
Comment 10•3 years ago
|
||
Comment 11•3 years ago
|
||
bugherder |
Reporter | ||
Comment 12•3 years ago
•
|
||
This caused an unused whitelist entry on Linux and macOS, patch incoming.
Reporter | ||
Comment 13•3 years ago
|
||
The exception got added in this bug, the usage of the CSS rule in bug 1696132
which started the Windows-only failures.
Comment 14•3 years ago
|
||
Comment 15•3 years ago
|
||
bugherder |
Comment hidden (Intermittent Failures Robot) |
Comment 17•3 years ago
|
||
Verified in today's central-as-beta simulation.
Comment hidden (Intermittent Failures Robot) |
Reporter | ||
Comment 19•3 years ago
|
||
bugherder uplift |
Updated•3 years ago
|
Description
•