>Not for now. Once it starts being green I could enable it with few
>locales to see how it behaves? what do you think?
>
>BTW for the curious, you can see the builder all the way to the right in
>here:
>http://tinderbox.mozilla.org/showbuilds.cgi?tree=Firefox&noignore=1
>as:
>WINNT 6.1 x86-64 mozilla-central *
>I will have debug, opt and xulrunner nightly builds. You will probably
>see several builds per day until I get everything to run smoothly.
where i can download the builds?
bye,
Sascha
--
"Not everyone understands House Music; it's a spiritual thing;
a body thing; a soul thing." - Eddie Amador
(c)
I will do a blog post and reply to the thread once I have them.
Cheers,
Armen
>Once the builds start working (I almost have them) they will show up in:
>http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-trunk/
>
>I will do a blog post and reply to the thread once I have them.
thx 4 the info. Right, that there is still no (pre)release of the
flash-plugin 4 64bit on windows?
Depends, what are we doing these builds for? If we're doing them for
releasing them, it'll be all locales, of course. Otherwise, I don't know.
Axel
Cheers,
Armen
Note that we do not have a pool of slaves yet. We could enable one or
two l10n repacks as a test, but not the full set until we ramp up the pool.
I don't think that there's a benefit in one or two locales. I'm fine
with the l10n repacks being blocked by building the necessary pool, as
long as the builds are there in time for testing before shipping. Not
sure what that means, though :-)
Axel
> Note that we do not have a pool of slaves yet. We could enable one or
> two l10n repacks as a test, but not the full set until we ramp up the pool.
Note that technically I don't think you have to have a win64 slave to repack
win64 builds: you could probably do it on a win32 slave. But it's probably
not worth worrying about until the builds actually work.
--BDS
Axel, thats the right priority.
To set context here, remember that this post is about setting up one
potential slave so that RelEng and developers figure out what toolchain
is needed in the reference image, what mozconfig settings to use and any
blocker code issues that need to be resolved.
Once we get *a* build that will actually run, then we've still got many
steps ahead of us, including setting up pool-o-slaves and doing l10n
repacks, before we get close to releasing win7x64 builds.
For now, lets keep this thread on the topic where we need the most help
- finding people with win64 expertise to help figure out how to get one
enUS build that actually will run.
tc
John.
-- Makoto
Armen Zambrano Gasparnian wrote:
> Hi all,
> In bug 547154 [1] I am setting up a Windows 64 bit machine to produce 64
> bit builds.
>
> Automation-wise I am ready to post the builds to the Firefox tinderbox
> page (hidden until we get developer fixes for the build bustages) and
> make the builds available on ftp. I will start posting them by the EOD.
>
> == What to expect ==
> This is our single builder and will be running once a day and every time
> a developer requests to trigger it (we would not be able to keep up on
> checkin).
> I still have to install more automation tools (nagios, OPSI and others)
> and I will do so while it is idle.
>
> == Where to help ==
> Makoto has a tracking bug [2] for the Win64 builds where there are
> plenty of bugs to help out. Most of the bugs are simple few liners like
> bug 567720 [3].
>
> Can anyone tell me what the right mozconfig should be?
> I started with this:
> http://hg.mozilla.org/users/armenzg_mozilla.com/buildbot-configs/file/4625d2ef00ff/mozilla2-staging/win64/mozilla-central/nightly/mozconfig
>
> but I will be trying to get something closer to what win32 does:
> http://hg.mozilla.org/users/armenzg_mozilla.com/buildbot-configs/file/4625d2ef00ff/mozilla2-staging/win32/mozilla-central/nightly/mozconfig
>
>
> If you are interested on helping please contact me and I will keep you
> in the loop with few other people who have already shown their interest
> on helping out.
>
> == Plan ==
> * tackle red builds
> * once green, unhide the builds
> * add remaining tools-chain
> * allocate slaves and clone
> * try server
> * talos w7-64 (commencing in Q2 but will slip into Q3)
> * unit tests w7-64 (commencing in Q2 but will slip into Q3)
>
> == Feedback ==
> As you can see I am trying to get things working as fast as possible
> trying to get people to fix things early rather than having to wait on
> me setting up automation tools, allocate slaves to clone from and others.
>
> Please let me know what things are blocking you and/or what things are
> not running correctly. Input is welcome.
>
>
> == References ==
> [1] Bug 567154 - Configure single buildslave in production to generate
> nightly Windows 64-bit builds
> https://bugzilla.mozilla.org/show_bug.cgi?id=567154
>
> [2] Bug 471090 - (tracking_win64) [meta] Windows x64 build tracking bug
> https://bugzilla.mozilla.org/show_bug.cgi?id=471090
>
> [3] Bug 567720 - bustage on x64 build for COMMessageFilter.cpp
> https://bugzilla.mozilla.org/show_bug.cgi?id=567720
>
I will be updating them in here:
http://hg.mozilla.org/users/armenzg_mozilla.com/buildbot-configs/file/tip/mozilla2-staging/win64/mozilla-central/nightly/mozconfig
http://hg.mozilla.org/users/armenzg_mozilla.com/buildbot-configs/file/tip/mozilla2-staging/win64/mozilla-central/debug/mozconfig
Armen