Closed
Bug 665331
Opened 13 years ago
Closed 13 years ago
Run Android jsreftests on Try
Categories
(Release Engineering :: General, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 666647
People
(Reporter: philor, Unassigned)
References
Details
At least, it seems there isn't any way to persuade them to run: none of -u all or -u jsreftest or -u jsreftest1,jsreftest-2 make them appear, which means bug 662468 will not be getting fixed, which means I've hidden them on every tree where they are running, and they're a total waste of resources until we can try to fix them on try. (And so personally, I'd treat the summary as meaning "on Try, and only on Try," though I don't know how much work it is to shut them off on m-c/m-i/TM and then turn them back on.)
Comment 1•13 years ago
|
||
marking this bug as a dupe of 664857, and will expand that bug to cover this as well.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
Reporter | ||
Comment 2•13 years ago
|
||
Well, let's dupe it to exactly and precisely what I filed it for, filed for exactly and precisely the reason I filed it.
Assignee | ||
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•