I would like to keep things green as much as possible by unhidding those
jobs that are already green. 
If there are no objections I will unhide them for mozilla-central
This is all preparatory work to fully support Windows 64-bit as a tier-1
Read below for status, bugs (volunteers needed) and tracking bug.
- we are cloning more build machines
- we don't have leak builds (see bugs below)
- mochitest-1 is the only suite with perma-oranges
- we don't have capacity for all branches but will eventually do
Bugs (Help needed):
- bug 669384 - make buildsymbols fails for leak test builds
- bug 670915 - make package fails for leak test builds
- bug 670697 - sporadic make check failures
- bug 671567 - WebGL failures for Windows 7 64-bit (mochitest-1)
- Bug 558448 - [Tracking bug] officially support Windows 64-bit builds
On Jul 14, 2:16 pm, Armen Zambrano Gasparnian <arme...@mozilla.com>
Why are there only opt Win64 builds, but no debug builds? (Sorry if
that was answered elsewhere.)
Objection. Loud, strident, red-faced shouting objection.
Things visible on mozilla-central are things which, if you break them,
you must back out. Simply, unequivocally.
After you back out, then you should fix your failures on try, and vow
next time to use try before you push. If you pushed a merge from an
integration branch, then you should either use your branch better, or
shout about how your branch has been handicapped, because it isn't
running everything it needs to run to tell you whether or not you are in
shape to merge.
If it isn't running on try, and it wasn't just an oversight that it's
not running on some integration branch, then it is absolutely without
question not ready to be visible on mozilla-central.
I understand that that makes the "get it green, making sure none of the
failures require changes on slaves" process more difficult; I've watched
&noignore=1 and filed the bugs on lots of previous platform changes and
additions. I know it's hard and frustrating. That doesn't change the
fact that mozilla-central is very much not "where you can make something
visible to get developer attention."
I've rehidden all the win64 tests. Sorry :(
Please have some mercy as I am trying to enable things as fast as I
From releng's priorities we have two:
* Try capacity
* Win7x64 testers. We currently don't have enough capacity. I will
explain more in a following post.
Yesterday's status update (today the builds actually compile):
On 11-09-07 4:47 PM, Phil Ringnalda wrote:
> On Wed, Sep 7, 2011 at 1:10 PM, armenzg<arm...@mozilla.com> wrote:
>> We now have try support for win64.
>> I will unhide the builds tomorrow when the orange builds are surpassed
>> by several green builds.
I disabled win64 coverage with all branches that have nightly builds
until I could manage to get green builds on mozilla-central (See bug
681158). We will re-enable it on the next few days until all project
branches have imported from mozilla-central.
The problem was that win64 was permanently orange and that was
preventing the nightly builds to be generated (we have a logic to take
the last green for all platforms; win64 was orange). Not sure why this
had not affected mozilla-central at all.
Let me know if you have any further questions.
On 11-09-07 4:53 PM, Kyle Huey wrote:
Everything should be good now.
Everything should be good now.
On 11-09-07 5:12 PM, Andrew McCreight wrote: