1800182 - Intermittent TV [tier 2] accessible/tests/browser/e10s/browser_caching_relations_002.js | single tracking bug

Status: RESOLVED FIXED

(Core :: Disability Access APIs, defect, P5)

Description

[Treeherder Bug Filer]

Filed by: mlaza [at] mozilla.com
Parsed log: https://treeherder.mozilla.org/logviewer?job_id=396240531&repo=autoland
Full log: https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/HBwp_8A9QyCYFycKn0ohoQ/runs/0/artifacts/public/logs/live_backing.log
Reftest URL: https://hg.mozilla.org/mozilla-central/raw-file/tip/layout/tools/reftest/reftest-analyzer.xhtml#logurl=https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/HBwp_8A9QyCYFycKn0ohoQ/runs/0/artifacts/public/logs/live_backing.log&only_show_unexpected=1

---

[task 2022-11-11T01:15:51.943Z] 01:15:51     INFO - TEST-PASS | accessible/tests/browser/e10s/browser_caching_relations_002.js | Actually remote browser - 
[task 2022-11-11T01:15:51.943Z] 01:15:51     INFO - Testing  relation of 'links to' type for '[DOM node id: link, role: link, name: 'Origin', address: [xpconnect wrapped nsIAccessible]]'.
[task 2022-11-11T01:15:51.944Z] 01:15:51     INFO - Fetched 0 relations from cache, looking for 1
[task 2022-11-11T01:15:51.944Z] 01:15:51     INFO - Buffered messages logged at 01:15:51
[task 2022-11-11T01:15:51.944Z] 01:15:51     INFO - Fetched 0 relations from cache, looking for 1
[task 2022-11-11T01:15:51.945Z] 01:15:51     INFO - Buffered messages finished
[task 2022-11-11T01:15:51.945Z] 01:15:51     INFO - TEST-UNEXPECTED-FAIL | accessible/tests/browser/e10s/browser_caching_relations_002.js | Found correct number of expected relations - 
[task 2022-11-11T01:15:51.946Z] 01:15:51     INFO - Stack trace:
[task 2022-11-11T01:15:51.946Z] 01:15:51     INFO - chrome://mochikit/content/browser-test.js:test_ok:1457
[task 2022-11-11T01:15:51.946Z] 01:15:51     INFO - chrome://mochitests/content/browser/accessible/tests/browser/shared-head.js:untilCacheOk/<:870
[task 2022-11-11T01:15:51.946Z] 01:15:51     INFO - [DOM node id: anchor, role: link, name: 'Destination', address: [xpconnect wrapped nsIAccessible]] could not be found in relation:  relation of 'links to' type for '[DOM node id: link, role: link, name: 'Origin', address: [xpconnect wrapped nsIAccessible]]'.
[task 2022-11-11T01:15:56.827Z] 01:15:56     INFO - [DOM node id: anchor, role: link, name: 'Destination', address: [xpconnect wrapped nsIAccessible]] could not be found in relation:  relation of 'links to' type for '[DOM node id: link, role: link, name: 'Origin', address: [xpconnect wrapped nsIAccessible]]'.
[task 2022-11-11T01:15:56.829Z] 01:15:56     INFO - Not taking screenshot here: see the one that was previously logged
[task 2022-11-11T01:15:56.829Z] 01:15:56     INFO - TEST-UNEXPECTED-FAIL | accessible/tests/browser/e10s/browser_caching_relations_002.js | All given related accessibles are targets of fetched relation. - 
[task 2022-11-11T01:15:56.829Z] 01:15:56     INFO - Stack trace:
[task 2022-11-11T01:15:56.829Z] 01:15:56     INFO - chrome://mochikit/content/browser-test.js:test_ok:1457
[task 2022-11-11T01:15:56.830Z] 01:15:56     INFO - chrome://mochitests/content/browser/accessible/tests/browser/shared-head.js:untilCacheOk/<:870
[task 2022-11-11T01:15:56.832Z] 01:15:56     INFO - TEST-PASS | accessible/tests/browser/e10s/browser_caching_relations_002.js | No unexpected targets found. - 

Comment 1

[BugBot [:suhaib / :marco/ :calixte]]

:morgan, since you are the author of the regressor, bug 1800060, could you take a look?

For more information, please visit auto_nag documentation.

Comment 2

[BugBot [:suhaib / :marco/ :calixte]]

Set release status flags based on info from the regressing bug 1800060

Comment 3

[Intermittent Failures Robot]

4 failures in 3445 pushes (0.001 failures/push) were associated with this bug in the last 7 days.

Repository breakdown:

• autoland: 4

Platform and build breakdown:

• windows10-64-2004-qr: 2
  • debug: 1
  • opt: 1
• windows10-32-2004-qr: 2
  • debug: 1
  • opt: 1

For more details, see:
https://treeherder.mozilla.org/intermittent-failures/bugdetails?bug=1800182&startday=2022-11-07&endday=2022-11-13&tree=all

Comment 4

[Morgan Reschenberg [:morgan]]

This seems to be the relevant part of the logs:

Testing  relation of 'links to' type for '[DOM node id: link, role: link, name: 'Origin', address: [xpconnect wrapped nsIAccessible]]'.
INFO - Fetched 0 relations from cache, looking for 1
INFO - Buffered messages logged at 01:15:51
INFO - Fetched 0 relations from cache, looking for 1
 INFO - Buffered messages finished
INFO - TEST-UNEXPECTED-FAIL | accessible/tests/browser/e10s/browser_caching_relations_002.js | Found correct number of expected relations - 
- [DOM node id: anchor, role: link, name: 'Destination', address: [xpconnect wrapped nsIAccessible]] could not be found in relation:  relation of 'links to' type for '[DOM node id: link, role: link, name: 'Origin', address: [xpconnect wrapped nsIAccessible]]'.
INFO - [DOM node id: anchor, role: link, name: 'Destination', address: [xpconnect wrapped nsIAccessible]] could not be found in relation:  relation of 'links to' type for '[DOM node id: link, role: link, name: 'Origin', address: [xpconnect wrapped nsIAccessible]]'.
TEST-UNEXPECTED-FAIL | accessible/tests/browser/e10s/browser_caching_relations_002.js | All given related accessibles are targets of fetched relation. - 

INFO - TEST-PASS | accessible/tests/browser/e10s/browser_caching_relations_002.js | No unexpected targets found. - 

:Jamie it looks like we sometimes aren't pushing LINKS_TO on windows. Bug 1800048 wouldn't have affected that, right? Since we're not using IA2 methods to do the relation retrieval?
🤔

Comment 5

[James Teh [:Jamie]]

(In reply to Morgan Reschenberg [:morgan] from comment #4)

:Jamie it looks like we sometimes aren't pushing LINKS_TO on windows.

This failure is without the cache, right? So we don't really push anything here.

Bug 1800048 wouldn't have affected that, right?

Bug 1800048 bounced because of this same failure, except not on verify. 😕 Maybe this was accidentally filed while that bug was still in the tree (before it got backed out)?

Since we're not using IA2 methods to do the relation retrieval?

Without the cache, Windows always uses IA2 methods to do the retrieval. That's exactly what the bug is here.

This didn't fail locally for me, but I'm guessing maybe I hadn't picked up latest mozilla-central when I tried it. The timing probably makes sense; you only landed the latest LINKS_TO patch pretty recently. I'll take a look at this today and see if I can get both this bug and my bug resolved. :)

Comment 6

[James Teh [:Jamie]]

I'm fairly sure this got filed while the original patch for bug 1800048 was still present. Since that was backed out, this should be fixed and my updated patch should address this.

Comment 7

[BugBot [:suhaib / :marco/ :calixte]]

Set release status flags based on info from the regressing bug 1800060