1903927 - Permanent failure /css/css-view-transitions/only-child-view-transition.html | single tracking bug

Status: RESOLVED DUPLICATE of bug 1904157

(Core :: CSS Parsing and Computation, defect)

Description

[Treeherder Bug Filer]

Filed by: istorozhko [at] mozilla.com
Parsed log: https://treeherder.mozilla.org/logviewer?job_id=462067065&repo=try
Full log: https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/PJnn5hmETvWHG8m75A3BTg/runs/0/artifacts/public/logs/live_backing.log

---

This test fails on all Android Fission builds,
with both `isolate-everything` and `isolate-high-value` Fission site isolation strategies.

Filed using Intermittent Filer, but this failure is permanent.

Blocks Fission on Android

Comment 1

[Daniel Holbert [:dholbert]]

The test has a special failure annotation for android-with-fission right now, which I guess is incorrect? It's expecting an error, but the log shows
that no error was encountered (TEST-UNEXPECTED-OK | /css/css-view-transitions/only-child-group.html | expected ERROR)

Here's the annotation with the special android-with-fission annotation:
https://searchfox.org/mozilla-central/rev/e729cdd1537458f9268215c2ff6dddb231c3a6d9/testing/web-platform/meta/css/css-view-transitions/only-child-view-transition.html.ini#1-5

[only-child-view-transition.html]
  expected:
    if (os == "android") and fission: [ERROR, TIMEOUT]
  [:only-child is not supported on view-transition]
    expected: FAIL

Does the issue go away if you remove the android-with-fission annotation? i.e. remove these two lines from that^ file:

  expected:
    if (os == "android") and fission: [ERROR, TIMEOUT]

Comment 2

[[:owlish] 🦉 PST]

Hi Daniel, I replied in bug 1903914. Basically, my question is, if we set the current annotations aside for a second, does this test actually supposed to pass or fail? What is the correct behaviour with Fission?

Comment 3

[Daniel Holbert [:dholbert]]

See my answer in bug 1903914 comment 4; it applies to all of these bugs. (There's no reason for there to be an android-with-fission specific expectation in any of these, aside from the fact that it was previously broken and we were annotating that known-breakage.)

does this test actually supposed to pass or fail?

This test is testing a feature that we don't support yet (view transitions), so parts of it are expected to fail (per the non-platform-specific expected: FAIL annotation quoted at the end of comment 1)

It's not expected to error or timeout, though; that seems to have been an annotation to reflect known breakage that we previously were hitting with android+fission, but happily are not hitting anymore, I guess.