Closed Bug 1244707 Opened 8 years ago Closed 6 years ago

Intermittent browser_webconsole_bug_632817.js | Test timed out (sometimes preceded by "A promise chain failed to handle a rejection: - TypeError: content.wrappedJSObject.testXhrGet is not a function")

Categories

(DevTools :: Console, defect, P3)

Product:
DevTools
Component:
Console
Type:
defect

Tracking

(firefox50 wontfix, firefox51 wontfix, firefox52 wontfix)

Status:
RESOLVED INVALID
Tracking Flags:
Tracking Status
firefox50 --- wontfix
firefox51 --- wontfix
firefox52 --- wontfix

People

(Reporter: philor, Unassigned)

Details

(Keywords: intermittent-failure, Whiteboard: [btpp-backlog][console-rewrite-fix][test-disabled])

Attachments

(1 file)

skip browser_webconsole_bug_632817.js
696 bytes, patch
linclark
: review+
Details | Diff | Splinter Review 
6 total, 5 in the last month. 3 this week.
Priority: -- → P3
Whiteboard: [btpp-backlog]
Summary: Intermittent browser_webconsole_bug_632817.js | Test timed out → Intermittent browser_webconsole_bug_632817.js | Test timed out (sometimes preceded by "A promise chain failed to handle a rejection: - TypeError: content.wrappedJSObject.testXhrGet is not a function")
This will be rewritten as part of the console frontend rewrite currently going on.
Whiteboard: [btpp-backlog] → [btpp-backlog][console-rewrite-fix]
(In reply to Lin Clark [:linclark] from comment #3)
> This will be rewritten as part of the console frontend rewrite currently
> going on.

Is someone (you?) still working on that? Will a fix/rewrite be available soon?
Flags: needinfo?(lclark)
The new console output (which is on in Nightly) has its own test for this. This test will be removed when the old frontend is removed. That won't be for a while yet, though, because we still need to convert the browser console to use the new console output.

If getting rid of this orange is high priority, we can skip this test. It's unlikely that this will break in the old frontend between now and when it's removed.
Flags: needinfo?(lclark)
Thanks Lin. Failures have been frequent for the last couple of weeks, so if you are not too concerned about the loss of coverage, yes, I think skipping is a good idea.
Attachment #8800280 - Flags: review?(lclark)
Attachment #8800280 - Flags: review?(lclark) → review+
Pushed by gbrown@mozilla.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/ef30e94ef7f4
Skip test browser_webconsole_bug_632817.js; r=linclark
Keywords: leave-open
Whiteboard: [btpp-backlog][console-rewrite-fix] → [btpp-backlog][console-rewrite-fix][test-disabled]
We should probably just remove the test and wontfix this bug if we have no intention of ever fixing the test.
status-firefox50: --- → wontfix
status-firefox51: --- → wontfix
status-firefox52: --- → wontfix
Whiteboard: [btpp-backlog][console-rewrite-fix][test-disabled] → [btpp-backlog][console-rewrite-fix][test-disabled][checkin-needed-aurora][checkin-needed-beta]
https://hg.mozilla.org/releases/mozilla-aurora/rev/0c4ba72824a2
Whiteboard: [btpp-backlog][console-rewrite-fix][test-disabled][checkin-needed-aurora][checkin-needed-beta] → [btpp-backlog][console-rewrite-fix][test-disabled][checkin-needed-beta]
> We should probably just remove the test and wontfix this bug if we have no intention of ever fixing the test.

While the old code is still being used in the browser console, I would rather have a record of the things we know that we aren't testing in it anymore. I don't think it will break since we aren't really touching that code anymore, but just in case it were to break and someone were to file an issue, we'd have a record of the fact that we used to test it and why the test was turned off.
https://hg.mozilla.org/releases/mozilla-beta/rev/0c814006e792
Whiteboard: [btpp-backlog][console-rewrite-fix][test-disabled][checkin-needed-beta] → [btpp-backlog][console-rewrite-fix][test-disabled]
Product: Firefox → DevTools
All the console tests were migrated and rewritten when we enabled the new console. If they're intermittent, new bugs were probably created.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: