Closed
Bug 638846
Opened 14 years ago
Closed 14 years ago
enable crashtest, jsreftest on tegras
Categories
(Release Engineering :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: bhearsum, Assigned: bear)
References
Details
Attachments
(3 files, 1 obsolete file)
|
920 bytes,
patch
|
mozilla
:
review+
bear
:
checked-in+
|
Details | Diff | Splinter Review |
|
1.13 KB,
patch
|
bhearsum
:
review+
mozilla
:
checked-in+
|
Details | Diff | Splinter Review |
|
2.32 KB,
patch
|
mozilla
:
review+
bear
:
checked-in+
|
Details | Diff | Splinter Review |
Blocked on issues with remotereftest.py.
| Reporter | ||
Comment 1•14 years ago
|
||
Joel advised me that it's best to run the jsreftest tests in 2 chunks, too.
Haven't been able to verify this in staging, because all of the foopy02 tegras are dead :(
This patch fixes bug 638844 too.
Attachment #518716 -
Flags: review?(aki)
Comment 2•14 years ago
|
||
Comment on attachment 518716 [details] [diff] [review]
enable crashtest and jsreftest
r=me, as this patch looks correct to re-enable crashtest and enable jsreftest in 2 chunks.
However, as of yesterday morning's quick meeting with bear/coop/joduinn/me, we heard that reftests were potentially taking out tegras in the production pool, so I'd rather not enable in production until we figure out what's going on.
If {jsref,ref,crash}tests all run in staging cleanly without a larger-than-expected lossage of tegras, let's turn 'em on. Otherwise turning off reftests and waiting for a fix might be a better immediate solution.
Attachment #518716 -
Flags: review?(aki) → review+
| Assignee | ||
Comment 3•14 years ago
|
||
taking bug to land and enable in new production pools
Assignee: bhearsum → bear
| Assignee | ||
Comment 4•14 years ago
|
||
Comment on attachment 518716 [details] [diff] [review]
enable crashtest and jsreftest
committed changeset 3865:d892db03a7fb
landed on default, will post when merged to production
Attachment #518716 -
Flags: checked-in+
Comment 5•14 years ago
|
||
per discussion in irc (for joel)
Attachment #523364 -
Flags: review?(bhearsum)
| Reporter | ||
Updated•14 years ago
|
Attachment #523364 -
Flags: review?(bhearsum) → review+
Comment 6•14 years ago
|
||
Comment on attachment 523364 [details] [diff] [review]
attaching a reftest patch because i'm a rebel
http://hg.mozilla.org/build/buildbot-configs/rev/8781a228b71b
Attachment #523364 -
Flags: checked-in+
| Assignee | ||
Comment 7•14 years ago
|
||
Attachment #523377 -
Flags: review?(aki)
| Assignee | ||
Comment 8•14 years ago
|
||
moved new step to top of routine to avoid having two identical pieces of code in the if/elif section
Attachment #523377 -
Attachment is obsolete: true
Attachment #523377 -
Flags: review?(aki)
Attachment #523381 -
Flags: review?(aki)
Comment 9•14 years ago
|
||
Comment on attachment 523381 [details] [diff] [review]
add config.py step to switch tegra resolution
This could also go above the 'for suite in' line, but I don't particularly care.
This looks good, and I think config.py's testname check will work out of the box, so r=me.
Attachment #523381 -
Flags: review?(aki) → review+
Updated•14 years ago
|
Summary: enable jsreftest on tegras → enable crashtest, jsreftest on tegras
| Assignee | ||
Comment 11•14 years ago
|
||
Comment on attachment 523381 [details] [diff] [review]
add config.py step to switch tegra resolution
committed changeset 1449:f56862ba640b
Attachment #523381 -
Flags: checked-in+
| Assignee | ||
Comment 12•14 years ago
|
||
moved to production by changeset 157a12ba4a76
| Assignee | ||
Comment 13•14 years ago
|
||
marking as resolved - crashtest run has a configure devices step (and it worked!)
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Updated•12 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•