Closed
Bug 1107807
Opened 10 years ago
Closed 10 years ago
Add win64 shell builds on try, off by default
Categories
(Release Engineering :: General, defect)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: sfink, Assigned: sfink)
References
Details
Attachments
(1 file, 1 obsolete file)
|
1.23 KB,
patch
|
bhearsum
:
review+
|
Details | Diff | Splinter Review |
The fuzzers would like autogenerated win64 builds, and we want to be supporting win64 in general now.
|
Assignee | |
Comment 1•10 years ago
|
||
win64 builds still require some gecko tree code to be landed first, so start out with them off on try (and don't run them anywhere else yet).
Attachment #8532396 -
Flags: review?(bhearsum)
|
||
Updated•10 years ago
|
Attachment #8532396 -
Flags: review?(bhearsum) → review+
|
|
Assignee | |
Comment 2•10 years ago
|
||
|
|
Assignee | |
Comment 3•10 years ago
|
||
Oops, missed this piece. I couldn't find anything in the environment that let me know whether we wanted a win32 vs win64 build, since both are compiled on win64 builders afaict.
Attachment #8534015 -
Flags: review?(bhearsum)
|
|
Assignee | |
Comment 4•10 years ago
|
||
Comment on attachment 8534015 [details] [diff] [review]
Pass through the platform
Er, never mind. I'll fold this in with bug 1106707.
Attachment #8534015 -
Flags: review?(bhearsum)
|
||
Comment 5•10 years ago
|
||
|
|
Assignee | |
Updated•10 years ago
|
Attachment #8534015 -
Attachment is obsolete: true
|
|
Assignee | |
Updated•10 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
|
||
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
•