Permanent devtools/shared/commands/resource/tests/browser_resources_network_events.js | single tracking bug
Categories
(DevTools :: General, defect, P5)
Tracking
(firefox112 fixed, firefox113 fixed)
People
(Reporter: intermittent-bug-filer, Assigned: bomsy)
References
(Regressed 1 open bug)
Details
(Keywords: intermittent-failure, intermittent-testcase)
Attachments
(2 files, 1 obsolete file)
48 bytes,
text/x-phabricator-request
|
diannaS
:
approval-mozilla-beta-
|
Details | Review |
48 bytes,
text/x-phabricator-request
|
diannaS
:
approval-mozilla-beta+
|
Details | Review |
Filed by: archaeopteryx [at] coole-files.de
Parsed log: https://treeherder.mozilla.org/logviewer?job_id=407726580&repo=autoland
Full log: https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/ajgzGUw-Q_qrlS9BO2rb4g/runs/0/artifacts/public/logs/live_backing.log
This failure did not get logged since bug 1819134 caused a regression which got fixed in bug 1819445. The test will be disabled until the regressing change has been identified.
[task 2023-03-03T15:39:56.624Z] 15:39:56 INFO - TEST-PASS | devtools/shared/commands/resource/tests/browser_resources_network_events.js | The 'isNavigationRequest' attribute is correct -
[task 2023-03-03T15:39:56.624Z] 15:39:56 INFO - Buffered messages finished
[task 2023-03-03T15:39:56.626Z] 15:39:56 INFO - TEST-UNEXPECTED-FAIL | devtools/shared/commands/resource/tests/browser_resources_network_events.js | The 'blockedReason' attribute is correct - Got "unknown", expected "NS_BINDING_ABORTED"
[task 2023-03-03T15:39:56.626Z] 15:39:56 INFO - Stack trace:
[task 2023-03-03T15:39:56.626Z] 15:39:56 INFO - chrome://mochikit/content/browser-test.js:test_is:1510
[task 2023-03-03T15:39:56.627Z] 15:39:56 INFO - chrome://mochitests/content/browser/devtools/shared/commands/resource/tests/browser_resources_network_events.js:assertResources:313
[task 2023-03-03T15:39:56.628Z] 15:39:56 INFO - chrome://mochitests/content/browser/devtools/shared/commands/resource/tests/browser_resources_network_events.js:onAvailable:241
[task 2023-03-03T15:39:56.628Z] 15:39:56 INFO - resource://devtools/shared/commands/resource/resource-command.js:_notifyWatchers:872
[task 2023-03-03T15:39:56.628Z] 15:39:56 INFO - resource://devtools/shared/throttle.js:later:33
[task 2023-03-03T15:39:56.629Z] 15:39:56 INFO - resource://gre/modules/Timer.sys.mjs:notify:49
Comment 1•2 years ago
|
||
The failure did get logged since bug 1819134 caused a regression which got fixed
in bug 1819445. The test will be reenabled once the regressing change has been
identified.
Comment 3•2 years ago
|
||
We regressed this in https://bugzilla.mozilla.org/show_bug.cgi?id=1803546 and https://bugzilla.mozilla.org/show_bug.cgi?id=1819279.
Before those bugs we would always use ChromeUtils.getXPCOMErrorName
to try to get a more accurate blocked reason, but now we only do it for NS_ERROR_UNKNOWN_HOST.
Comment 4•2 years ago
•
|
||
Depends on D171577
Short summary of the history here: the assert which regressed was initially added in https://bugzilla.mozilla.org/show_bug.cgi?id=1745944
This is when we started using ChromeUtils.getXPCOMErrorName to get more accurate blockedReasons.
However after Bug https://bugzilla.mozilla.org/show_bug.cgi?id=1819279, we now only translate blockedReasons for NS_ERROR_UNKNOWN_HOST
Which leads all the other blocked reasons to show up as "unknown". Maybe this was the wrong call and we need to adjust the implementation, but this
patch at least makes the test consistent with the implementation so that we can re-enable it.
(the regression was not detected, because the harness was unexpectedly throwing in the middle of the test)
Updated•2 years ago
|
Comment 5•2 years ago
|
||
bugherder |
Updated•2 years ago
|
Updated•2 years ago
|
Comment hidden (Intermittent Failures Robot) |
Updated•2 years ago
|
Assignee | ||
Comment 8•2 years ago
|
||
Updated•2 years ago
|
Comment 10•2 years ago
|
||
bugherder |
Comment 11•2 years ago
|
||
The patch landed in nightly and beta is affected.
:jdescottes, is this bug important enough to require an uplift?
- If yes, please nominate the patch for beta approval.
- If no, please set
status-firefox112
towontfix
.
For more information, please visit auto_nag documentation.
Comment 12•2 years ago
|
||
Forwarding to Hubert.
Assignee | ||
Comment 13•2 years ago
|
||
Comment on attachment 9323012 [details]
Bug 1820200 - [devtools] Fix and enable browser_resources_network_events.js test r=#devtools-reviewers
Beta/Release Uplift Approval Request
- User impact if declined: Users may see unusual error requests
- Is this code covered by automated tests?: Yes
- Has the fix been verified in Nightly?: Yes
- Needs manual test from QE?: No
- If yes, steps to reproduce:
- List of other uplifts needed: None
- Risk to taking this patch: Low
- Why is the change risky/not risky? (and alternatives if risky): Low risk, fixes block error statuses.
- String changes made/needed:
- Is Android affected?: Yes
Assignee | ||
Updated•2 years ago
|
Comment 14•2 years ago
|
||
Comment on attachment 9323012 [details]
Bug 1820200 - [devtools] Fix and enable browser_resources_network_events.js test r=#devtools-reviewers
Approved for 112.0b6
Updated•2 years ago
|
Comment 15•2 years ago
|
||
bugherder uplift |
Description
•