Closed
Bug 1118799
Opened 11 years ago
Closed 10 years ago
Using async promises causes several tests in the timeline to fail
Categories
(DevTools :: Performance Tools (Profiler/Timeline), defect)
Tracking
(Not tracked)
RESOLVED
FIXED
Firefox 38
People
(Reporter: ejpbruel, Assigned: ejpbruel)
References
Details
Attachments
(2 files)
931 bytes,
patch
|
Details | Diff | Splinter Review | |
1.96 KB,
patch
|
pbro
:
review+
|
Details | Diff | Splinter Review |
In bug 1096490, I'm replacing the deprecated-sync-thenables promises, which are synchronous, with Promise.jsm promises, which are asynchronous. Doing so causes several tests in the timeline to fail.
To reproduce this issue, simply apply the attached patch.
Reporter | ||
Comment 1•11 years ago
|
||
Comment 2•11 years ago
|
||
Only test that's failing is browser_timeline_overview-update.js
Reporter | ||
Comment 3•11 years ago
|
||
According to Victor, the problem is that browser_timeline_overview-update.js assumes that using an about:blank page does not cause any markers to be recorded. However, this assumption turns out to be false. In particular, Styles markers are being recorded. I'm not exactly sure why this didn't happen with the deprecated-sync-thenables, but it must be some timing issue.
What's more, simply changing the test to ignore Style markers is not sufficient: doing so makes the test pass locally, but not on try. Apparently, we cannot rely on the behavior of an about:blank page wrt recording, which means that these assertions are currently useless.
I'm going to file a patch in this bug that disables the offending assertions, with a follow up bug to re-enable them once we figure out a way around this.
Reporter | ||
Comment 4•11 years ago
|
||
Attachment #8548131 -
Flags: review?(vporof)
Reporter | ||
Updated•11 years ago
|
Attachment #8548131 -
Flags: review?(vporof) → review?(pbrosset)
Comment 5•11 years ago
|
||
Comment on attachment 8548131 [details] [diff] [review]
Disable faulty assertions in browser_timeline_overview-update.js
Review of attachment 8548131 [details] [diff] [review]:
-----------------------------------------------------------------
Ok, disabling these assertions and filing a follow-up bug to re-enable them later sounds fine to me. We need to move away from the sync promises.
Attachment #8548131 -
Flags: review?(pbrosset) → review+
Reporter | ||
Comment 6•10 years ago
|
||
Try run for the above patch:
https://treeherder.mozilla.org/#/jobs?repo=try&revision=79d7e501d382
Reporter | ||
Comment 7•10 years ago
|
||
Try run looks green, pushing to fx-team:
https://hg.mozilla.org/integration/fx-team/rev/910019565e35
Assignee: nobody → ejpbruel
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 38
Comment 9•10 years ago
|
||
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)
Updated•7 years ago
|
Product: Firefox → DevTools
You need to log in
before you can comment on or make changes to this bug.
Description
•