Bugzilla

It's actually `TEST-UNEXPECTED-PASS`, not a failure. :)

The test's only annotation is:
https://searchfox.org/mozilla-central/rev/e729cdd1537458f9268215c2ff6dddb231c3a6d9/testing/web-platform/meta/css/cssom/CSSStyleSheet-constructable-concat.html.ini#1-3
```
[CSSStyleSheet-constructable-concat.html]
  expected:
    if (os == "android") and fission: [OK, TIMEOUT]
```

which looks like it's intending to allow the test to either pass or timeout.

I suspect the issue is the `OK` status there -- I think we use that for testharness.js-based tests, but for reftest-style tests (which this one is), we need `PASS` instead.

owlish, would you mind testing `s/OK/PASS/` in that^ .ini file and see if that fixes the issue?  Alternately: if this really does always pass, we could just remove the .ini file entirely, since it's expressing an allowance that we perhaps don't need anymore.

It's actually `TEST-UNEXPECTED-PASS`, not a failure. :)

The test's only annotation is:
https://searchfox.org/mozilla-central/rev/e729cdd1537458f9268215c2ff6dddb231c3a6d9/testing/web-platform/meta/css/cssom/CSSStyleSheet-constructable-concat.html.ini#1-3
```
[CSSStyleSheet-constructable-concat.html]
  expected:
    if (os == "android") and fission: [OK, TIMEOUT]
```

which looks like it's intending to allow the test to either pass or timeout.

I suspect the issue is the `OK` status there -- I think we use that for testharness.js-based tests, but for reftest-style tests (which this one is), we need `PASS` instead.

owlish, would you mind testing `s/OK/PASS/` in that^ .ini file and see if that fixes the issue?  Alternately: if this really does always pass, we could just remove the .ini file entirely, since it's expressing an allowance that we perhaps don't need anymore (and doing so in a way that's not-quite-right, per this bug).

It's actually `TEST-UNEXPECTED-PASS`, not a failure. :)

The test's only annotation is:
https://searchfox.org/mozilla-central/rev/e729cdd1537458f9268215c2ff6dddb231c3a6d9/testing/web-platform/meta/css/cssom/CSSStyleSheet-constructable-concat.html.ini#1-3
```
[CSSStyleSheet-constructable-concat.html]
  expected:
    if (os == "android") and fission: [OK, TIMEOUT]
```

which looks like it's intending to allow the test to either pass or timeout.

I suspect the issue is the `OK` status there -- I think we use that for testharness.js-based tests, but for reftest-style tests (which this one is), we need `PASS` instead.

~owlish, would you mind testing `s/OK/PASS/` in that^ .ini file and see if that fixes the issue?  Alternately: if this really does always pass, we could just remove the .ini file entirely, since it's expressing an allowance that we perhaps don't need anymore (and doing so in a way that's not-quite-right, per this bug).~

EDIT: it's probably not worth testing one-off tweaks here, per my next comment.)