Permanent failure on Fission /css/css-view-transitions/pseudo-computed-style-stays-in-sync-with-new-element.html
Categories
(Core :: CSS Parsing and Computation, defect)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox133 | --- | fixed |
People
(Reporter: intermittent-bug-filer, Assigned: emilio)
References
(Depends on 1 open bug)
Details
Filed by: istorozhko [at] mozilla.com
Parsed log: https://treeherder.mozilla.org/logviewer?job_id=478454745&repo=try
Full log: https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/M1IrMatLR9yrLoHpPHKb7Q/runs/0/artifacts/public/logs/live_backing.log
Filed using Intermittent bug filer, but the failure is permanent on Android Fission, both `isolateHighValue` and `isolateEverything` isolation strategies
Updated•1 year ago
|
Updated•1 year ago
|
Comment 1•1 year ago
|
||
Hi Emilio, we are getting ready to start Fission experiment in 135, I wonder if your team can take a look at this failure? Thank you!
Comment 2•1 year ago
|
||
Perhaps we can just mark this failed because we haven't implemented this yet.
Updated•1 year ago
|
| Assignee | ||
Comment 3•1 year ago
|
||
Yes, just update the expectations for now. I think you might just need to remove this line?
| Assignee | ||
Updated•1 year ago
|
Comment 5•1 year ago
|
||
| bugherder | ||
Updated•1 year ago
|
| Comment hidden (Intermittent Failures Robot) |
Comment 7•1 year ago
•
|
||
(In reply to Pulsebot from comment #4)
Pushed by emilio@crisal.io:
https://hg.mozilla.org/integration/autoland/rev/38ea1f6fbb70
Remove android+fission specific annotation.
Perfherder has detected a browsertime performance change from push 38ea1f6fbb7092424b20f31a4bb8626358139785.
Improvements:
| Ratio | Test | Platform | Options | Absolute values (old vs new) |
|---|---|---|---|---|
| 3% | speedometer3 TodoMVC-Backbone/CompletingAllItems/total | android-hw-a55-14-0-aarch64-shippable | webrender | 38.85 -> 37.79 |
| 2% | speedometer3 TodoMVC-Backbone/total | android-hw-a55-14-0-aarch64-shippable | webrender | 138.74 -> 135.95 |
Details of the alert can be found in the alert summary, including links to graphs and comparisons for each of the affected tests.
If you need the profiling jobs you can trigger them yourself from treeherder job view or ask a sheriff to do that for you.
You can run these tests on try with ./mach try perf --alert 2708
For more information on performance sheriffing please see our FAQ.
| Assignee | ||
Comment 8•1 year ago
|
||
This can't be right? This is a test only change.
Comment 9•1 year ago
|
||
I've edited the previous comment. Some alerts have ben reassigned to other revisions, but these two remained and indicate this revision as the culprit
| Assignee | ||
Comment 10•1 year ago
|
||
Still impossible. Way more likely to be the previous push which contains https://hg.mozilla.org/integration/autoland/rev/fbe9fbb6ae72d8b3ea3e411f83545915a5782fda)
Comment 11•1 year ago
|
||
I reassigned tho alerts to the revision you indicated.
Thanks for help with the investigation!
Description
•