disabling w2k3 & disabling jetpack (only perma-red ones)
armenzg
Tomorrow morning (6am PDT) I would like to let you know about this not
very noticeable changes:
* disable w2k3 debug unit tests (except for 1.9.1 & 1.9.2) [1]
* disable jetpack (only perma-reds) [2]
None of these will happen if it conflicts with the branch releases.
If you want to know about the improvements of these changes read at
the bottom.
I already have ACK from dev meeting last week for all changes.
All of these changes have been tested on staging and requires NO
DOWNTIME.
If you have any concerns let me know on this thread.
NOTE: I say "not very noticeable" because w2k3 test jobs and failing
jetpacks require you to use &noignore=1 with tbpl and tinderbox
cheers,
Armen
[1] https://bugzilla.mozilla.org/show_bug.cgi?id=614956
[2] https://bugzilla.mozilla.org/show_bug.cgi?id=627070
Details
######
With change #1 builds will more likely to wait less and be run on an
IX fast machine instead of a VM (less jobs/# slaves).
With change #2 we will improve our wait times as we are currenly:
* wasting CPU on perma-red jobs
* avoid win7 slaves getting hung for days because of jetpack
Mike Shaver
> Hello all,
> Tomorrow morning (6am PDT) I would like to let you know about this not
> very noticeable changes:
> * disable w2k3 debug unit tests (except for 1.9.1 & 1.9.2) [1]
> * disable jetpack (only perma-reds) [2]
Thanks, Armen. This'll help us ship.
Mike
Armen Zambrano Gasparnian
> On Wed, Jan 19, 2011 at 2:31 PM, armenzg<arm...@mozilla.com> wrote:
>> Hello all,
>> Tomorrow morning (6am PDT) I would like to let you know about this not
>> very noticeable changes:
>> * disable jetpack (only perma-reds) [2]
>
> Thanks, Armen. This'll help us ship.
>
> Mike
This has been completed without any problems.
Expect your Windows builds to have a higher chance of running on fast IX
machines and the pool of testing slaves to have less wait times (just a
little).
cheers,
Armen