Closed
Bug 696288
Opened 13 years ago
Closed 13 years ago
Regression: Processing.js Performance Tests don't work
Categories
(DevTools :: General, defect, P1)
Tracking
(firefox9+ fixed, firefox10+ fixed)
VERIFIED
FIXED
Firefox 10
People
(Reporter: dmandelin, Assigned: past)
References
()
Details
(Keywords: regression, verified-aurora, verified-beta, Whiteboard: [qa!][testcase: comment 3])
Attachments
(1 file)
2.02 KB,
patch
|
ddahl
:
review+
smaug
:
review+
christian
:
approval-mozilla-beta+
|
Details | Diff | Splinter Review |
[18:23:05.014] uncaught exception: TypeError: format.replace is not a function 9/20 nightly: works 9/21 nightly: doesn't work http://hg.mozilla.org/mozilla-central/pushloghtml?startdate=09%2F19%2F2011&enddate=09%2F21%2F2011
Reporter | ||
Comment 1•13 years ago
|
||
I bisected this to http://hg.mozilla.org/mozilla-central/rev/8e3e1c5f348d It appears that that patch introduces a call to |format.replace| on some paths called for console logging functions, and |format.replace| doesn't exist.
Blocks: 614586
Reporter | ||
Updated•13 years ago
|
Assignee: general → nobody
Component: JavaScript Engine → Developer Tools
Product: Core → Firefox
QA Contact: general → developer.tools
Assignee | ||
Comment 2•13 years ago
|
||
How can I reproduce this failure?
Comment 3•13 years ago
|
||
(In reply to Panos Astithas [:past] from comment #2) > How can I reproduce this failure? 1) go here: http://scotland.proximity.on.ca/dxr/tmp/processing-js/test/perf/ 2) click start
Assignee | ||
Updated•13 years ago
|
Assignee: nobody → past
Status: NEW → ASSIGNED
Assignee | ||
Comment 4•13 years ago
|
||
A simple fix with a test.
Attachment #569007 -
Flags: review?(ddahl)
Comment 5•13 years ago
|
||
Try run for 7e1cb1fada01 is complete. Detailed breakdown of the results available here: https://tbpl.mozilla.org/?tree=Try&rev=7e1cb1fada01 Results (out of 155 total builds): success: 152 warnings: 2 failure: 1 Builds available at http://ftp.mozilla.org/pub/mozilla.org/firefox/try-builds/pastithas@mozilla.com-7e1cb1fada01
Updated•13 years ago
|
Attachment #569007 -
Flags: review?(ddahl) → review+
Assignee | ||
Updated•13 years ago
|
Attachment #569007 -
Flags: review?(Olli.Pettay)
Updated•13 years ago
|
Attachment #569007 -
Flags: review?(Olli.Pettay) → review+
Assignee | ||
Updated•13 years ago
|
Whiteboard: [land-in-fx-team]
Comment 6•13 years ago
|
||
https://hg.mozilla.org/integration/fx-team/rev/7ba9a146e1e8
Whiteboard: [land-in-fx-team] → [fixed-in-fx-team]
Updated•13 years ago
|
Priority: -- → P1
Comment 7•13 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/7ba9a146e1e8
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Whiteboard: [fixed-in-fx-team]
Target Milestone: --- → Firefox 10
Assignee | ||
Comment 9•13 years ago
|
||
Comment on attachment 569007 [details] [diff] [review] Simple fix We forgot to get this into 9 when it was in aurora, can we get it into beta now?
Attachment #569007 -
Flags: approval-mozilla-beta?
Comment 10•13 years ago
|
||
Comment on attachment 569007 [details] [diff] [review] Simple fix [triage comment] Approved for beta. Please land today asap.
Attachment #569007 -
Flags: approval-mozilla-beta? → approval-mozilla-beta+
Comment 12•13 years ago
|
||
(In reply to Rob Campbell [:rc] (robcee) from comment #11) > http://hg.mozilla.org/releases/mozilla-beta/rev/3d16e65f9481 Can we change status-firefox9 to fixed?
Updated•13 years ago
|
Comment 13•13 years ago
|
||
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:9.0) Gecko/20100101 Firefox/9.0 (beta 3) Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0a2) Gecko/20111122 Firefox/10.0a2 Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:11.0a1) Gecko/20111122 Firefox/11.0a1 Mozilla/5.0 (Windows NT 6.1; WOW64; rv:11.0a1) Gecko/20111122 Firefox/11.0a1 Verified using the steps from comment #3: pressing "Start" started the tests run, although some tests failed. Should a separate bug be logged for that?
Status: RESOLVED → VERIFIED
Keywords: verified-aurora,
verified-beta
Whiteboard: [qa+][testcase: comment 3] → [qa!][testcase: comment 3]
Comment 14•13 years ago
|
||
(In reply to Mihaela Velimiroviciu [QA] from comment #13) > Mozilla/5.0 (Windows NT 6.1; WOW64; rv:9.0) Gecko/20100101 Firefox/9.0 (beta > 3) > Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0a2) Gecko/20111122 Firefox/10.0a2 > Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:11.0a1) Gecko/20111122 > Firefox/11.0a1 > Mozilla/5.0 (Windows NT 6.1; WOW64; rv:11.0a1) Gecko/20111122 Firefox/11.0a1 > > Verified using the steps from comment #3: pressing "Start" started the tests > run, although some tests failed. Should a separate bug be logged for that? no. If the processing team finds bugs in that version, they should open new bugs for the regressions. Thanks for verifying.
Updated•6 years ago
|
Product: Firefox → DevTools
You need to log in
before you can comment on or make changes to this bug.
Description
•