Bugzilla

comment 652 was actually ` load failed: timed out waiting for reftest-wait to be removed` for this test (598726-1.html) and several others (comparing 613433-1.html vs. its 3 reference cases)  All four of those `reftest.list` lines are flagged as `needs-focus`, so I suspect really they were blocked on gaining focus for some reason, and the test timed out for that reason.


That was on aarch64.  The previous comment 2 years earlier was also on aarch64, so it may have been the same issue -- can't know for sure since the logs have expired.

But in any case, that "timed out" issue (possibly focus-related, possibly aarch64-specific) seems unrelated to what this bug was originally tracking, which was a reftest failure with "image comparison (==)".  So let's close this as WFM. And hopefully any remaining aarch64/focus-related timeouts that trip over this test will spawn a new bug report which can be investigated with more recent data rather than 650 comments' worth of unrelated decades-old data. :)

The failure in comment 652 (the most recent failure) was actually ` load failed: timed out waiting for reftest-wait to be removed` for this test (598726-1.html) and several others (comparing 613433-1.html vs. its 3 reference cases)  All four of those `reftest.list` lines are flagged as `needs-focus`, so I suspect really they were blocked on gaining focus for some reason, and the test timed out for that reason.


That was on aarch64.  The previous comment 2 years earlier was also on aarch64, so it may have been the same issue -- can't know for sure since the logs have expired.

But in any case, that "timed out" issue (possibly focus-related, possibly aarch64-specific) seems unrelated to what this bug was originally tracking, which was a reftest failure with "image comparison (==)".  So let's close this as WFM. And hopefully any remaining aarch64/focus-related timeouts that trip over this test will spawn a new bug report which can be investigated with more recent data rather than 650 comments' worth of unrelated decades-old data. :)

The failure in comment 652 (the most recent failure) was actually ` load failed: timed out waiting for reftest-wait to be removed` for this test (598726-1.html) and one other test that gets run three times (613433-1.html vs. its 3 reference cases).  All four of those `reftest.list` lines are flagged as `needs-focus`, so I suspect really they were blocked on the reftest window failing to gain focus for some reason, and the test timed out for that reason.


That was on aarch64.  The previous comment 2 years earlier was also on aarch64, so it may have been the same issue -- can't know for sure since the logs have expired.

But in any case, that "timed out" issue (possibly focus-related, possibly aarch64-specific) seems unrelated to what this bug was originally tracking, which was a reftest failure with "image comparison (==)".  So let's close this as WFM. And hopefully any remaining aarch64/focus-related timeouts that trip over this test will spawn a new bug report which can be investigated with more recent data rather than 650 comments' worth of unrelated decades-old data. :)

The failure in comment 652 (the most recent failure) was actually ` load failed: timed out waiting for reftest-wait to be removed` for this test (598726-1.html) and one other test that gets run three times (613433-1.html vs. its 3 reference cases).  All four of those `reftest.list` lines are flagged as `needs-focus`, so I suspect really they were blocked on the reftest window failing to gain focus for some reason, and the test timed out for that reason.


That failure was on aarch64.  The previous comment 2 years earlier was also on aarch64, so it may have been the same issue -- can't know for sure since the logs have expired.

But in any case, the comment 652 [and maybe 651] "timed out" issue (possibly focus-related, possibly aarch64-specific) seems unrelated to what this bug was originally tracking, which was a reftest failure with "image comparison (==)".  So let's close this as WFM. And hopefully any remaining aarch64/focus-related timeouts that trip over this test will spawn a new bug report which can be investigated with more recent data rather than 650 comments' worth of unrelated decades-old data. :)

The failure in comment 652 (the most recent failure) was actually ` load failed: timed out waiting for reftest-wait to be removed` for this test (598726-1.html) and one other test that gets run three times (613433-1.html vs. its 3 reference cases).  All four of those `reftest.list` lines are flagged as `needs-focus`, so I suspect really they were blocked on the reftest window failing to gain focus for some reason, and the test timed out for that reason.


That failure was on aarch64.  The previous comment 2 years earlier was also on aarch64, so it may have been the same issue -- can't know for sure since the logs have expired.

But in any case, the comment 652 [and maybe 651] "timed out" issue (possibly focus-related, possibly aarch64-specific) seems unrelated to what this bug was originally tracking, which was a reftest failure with "image comparison (==)".  So let's close the original issue as WFM. And hopefully any remaining aarch64/focus-related timeouts that trip over this test will spawn a new bug report which can be investigated with more recent data rather than 650 comments' worth of unrelated decades-old data. :)