Closed
Bug 774282
Opened 13 years ago
Closed 13 years ago
turn on new jstests for mozilla-central
Categories
(Release Engineering :: General, defect, P3)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: jmaher, Unassigned)
References
Details
Attachments
(2 files)
1.32 KB,
patch
|
armenzg
:
review+
armenzg
:
checked-in+
|
Details | Diff | Splinter Review |
4.15 KB,
patch
|
armenzg
:
review+
|
Details | Diff | Splinter Review |
we have added new jstests to talos and disabled old ones. Now we have the kinks worked out and it is time to start running these new tests.
Reporter | ||
Comment 1•13 years ago
|
||
Attachment #642587 -
Flags: review?(armenzg)
Updated•13 years ago
|
Attachment #642587 -
Flags: review?(armenzg) → review+
Comment 2•13 years ago
|
||
Comment on attachment 642587 [details] [diff] [review]
run new jstests on mozilla-central to get a baseline (1.0)
Landed on "default":
ebd532bfd761
Attachment #642587 -
Flags: checked-in+
Comment 3•13 years ago
|
||
I hid the "jstests" on mozilla-central until they are green.
As usual noignore=1 can be used to see them:
https://tbpl.mozilla.org/?jobname=jstests
Reporter | ||
Comment 4•13 years ago
|
||
graph server definitions are updated, we just need to unhide these in due time.
Updated•13 years ago
|
Component: Release Engineering → Release Engineering: Automation (General)
QA Contact: catlee
Whiteboard: [testing][waiting to unhide]
Reporter | ||
Comment 5•13 years ago
|
||
unhidden from m-c, need to adjust the buildbot configs.
Reporter | ||
Comment 6•13 years ago
|
||
this should get these tests live for Firefox 17.
Attachment #647206 -
Flags: review?(armenzg)
Comment 7•13 years ago
|
||
Comment on attachment 647206 [details] [diff] [review]
turn on jstests (as dromaeo) and flip ts_places to dirty (1.0)
Can you put the "# Firefox 17/release" block before the "#### END OF MERGE DAY - EXCEPTIONS" line?
I don't see 'sunspider:kraken:v8_7', '--mozAfterPaint' being run with --mozAfterPaint anymore as I thought you were staging.
I will wait for your reply to review it.
Reporter | ||
Comment 8•13 years ago
|
||
The MozAfterPaint is an oversight on my part. The question is should we turn dromaeo_css|_dom running with mozafterpaint, or split this out in a separate testsuite. I prefer the MozAfterPaint change to dromaeo.
Reporter | ||
Comment 9•13 years ago
|
||
dmandelin: do you have a problem if we run the dromaeo_dom and dromaeo_css tests with mozafterpaint?
Updated•13 years ago
|
Priority: -- → P3
Updated•13 years ago
|
Attachment #647206 -
Flags: review?(armenzg) → review+
Comment 10•13 years ago
|
||
(In reply to Joel Maher (:jmaher) from comment #9)
> dmandelin: do you have a problem if we run the dromaeo_dom and dromaeo_css
> tests with mozafterpaint?
I don't think I'm affected, because those are DOM and layout tests.
Reporter | ||
Comment 11•13 years ago
|
||
great, I need to double check the graph server is configured properly, we can turn these on and resolve it later, either way early next week we should be live
Reporter | ||
Comment 12•13 years ago
|
||
Armen, do you want me to land this in the buildbot-configs repository? I have a bug in the works for the graph server adjustments.
Reporter | ||
Comment 13•13 years ago
|
||
landed:
http://hg.mozilla.org/build/buildbot-configs/rev/e85c12f3273a
waiting for reconfig.
Comment 14•13 years ago
|
||
deployed via reconfig today
Reporter | ||
Comment 15•13 years ago
|
||
Seeing results come in on the different platforms. Ready to close this out.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Whiteboard: [testing][waiting to unhide]
Assignee | ||
Updated•12 years ago
|
Product: mozilla.org → Release Engineering
Assignee | ||
Updated•7 years ago
|
Component: General Automation → General
You need to log in
before you can comment on or make changes to this bug.
Description
•