Closed Bug 1067953 Opened 10 years ago Closed 10 years ago

Intermittent browser_timelineMarkers-02.js | Test timed out - expected PASS

Categories

(DevTools :: Performance Tools (Profiler/Timeline), defect)

Product:
DevTools
Component:
Performance Tools (Profiler/Timeline)
Platform:
x86
Linux
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(firefox33 unaffected, firefox34 unaffected, firefox35 fixed, firefox-esr31 unaffected)

Status:
RESOLVED FIXED
Milestone:
Firefox 35
Tracking Flags:
Tracking Status
firefox33 --- unaffected
firefox34 --- unaffected
firefox35 --- fixed
firefox-esr31 --- unaffected

People

(Reporter: cbook, Assigned: pbro)

References

(
URL
)

Details

(Keywords: intermittent-failure)

Attachments

(1 file)

bug1067953-disabling-browser_timelineMarkers-02.js-again.patch
796 bytes, patch
pbro
: review+
Details | Diff | Splinter Review 
Ubuntu VM 12.04 mozilla-inbound opt test mochitest-e10s-browser-chrome-2 on 2014-09-16 04:03:46 PDT for push ba2fd2f25d4e

slave: tst-linux32-spot-349

https://tbpl.mozilla.org/php/getParsedLog.php?id=48184747&tree=Mozilla-Inbound

115 INFO TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/docshell/test/browser/browser_timelineMarkers-02.js | Test timed out - expected PASS
So this is basically permafailing. I'm going to be looking for a bisect & backout in the very near future.
Component: General → Developer Tools: Timeline
Flags: needinfo?(paul)
The failing test was previously disabled because it wasn't passing on e10s, but not for the same reasons I'm seeing here. It used to fail because of an xray array wrapper that wasn't giving access to some properties that we needed in the test. So, something directly related to the test itself.

I recently work again on that test to try and enable it, and it seemed that the xray wrapper behavior had changed because the test suddenly started to pass again, with no changes. For instance, this try build: https://tbpl.mozilla.org/?tree=Try&rev=adcc5f534e66 shows the test passing fine on linux e10s.

So, I re-enabled the test using bug 1064848, which landed on m-c on the 2 days ago.

Now, looking at these new failures, I can see hundreds of the same logs:

16:36:44     INFO -  JavaScript error: resource://gre/components/multiprocessShims.js, line 80: NS_ERROR_UNEXPECTED: Unexpected error
16:36:44     INFO -  JavaScript error: , line 0: Error: operation not possible on dead CPOW

which doesn't seem to be directly related to the test at all.
Apparently, the test starts, and then these errors are generated several times per seconds for, like, several minutes, until the test times out.

I have no idea how this relates to the test, so I think for now the best is to disable it again until we find out what's going on.
Assignee: nobody → pbrosset
Status: NEW → ASSIGNED
Flags: needinfo?(paul)
https://hg.mozilla.org/mozilla-central/rev/a78ec4ea3f52
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 35
Sorry for the spam. Moving bugs to Firefox :: Developer Tools: Performance Tools (Profiler/Timeline).

dkl
Component: Developer Tools: Timeline → Developer Tools: Performance Tools (Profiler/Timeline)
Product: Firefox → DevTools
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: