515357 - Thunderbird 3.0 l10n nightly builds slow?

Status: RESOLVED WORKSFORME

(Mozilla Messaging Graveyard :: Server Operations, defect)

Description

[Stefan Plewako [:stef]]

The last nightly linux (2009/09/08) build for pl locale started at 21:22 and ended as testfailed (it shouldn't) - that's insane.

Don't know if it is not enough resources or software problem but if it will escalate like in last weeks it will have big negative impact on our testing process.

Comment 1

[Mark Banner (:standard8)]

(In reply to comment #0)
> The last nightly linux (2009/09/08) build for pl locale started at 21:22 and
> ended as testfailed (it shouldn't) - that's insane.

It helps us if you provide a log reference. I'm assuming you mean this build:

http://tinderbox.mozilla.org/showlog.cgi?log=Mozilla-l10n-pl/1252470179.1252470634.21481.gz

From the tinderbox page, revisions are:

comm_revision: 1a6524fa578d
moz_revision: 0a86b30c95ce
l10n_revision: c53fcbaae2c4

So these are the revision numbers of the 2009/09/08 nightly.

It does seem a little late for the builds to start. This feels like our builders were too busy with the normal trunk builds to get to the l10n builds, but passing to gozer to take a look at it.

> Don't know if it is not enough resources or software problem but if it will
> escalate like in last weeks it will have big negative impact on our testing
> process.

Last weeks? I do not remember seeing a bug or any message/complaint about it. We can't do/check anything if we're not told. Please remember our system is a different set of boxes to the MoCo (Firefox) system.

Comment 2

[Stefan Plewako [:stef]]

(In reply to comment #1)
> It helps us if you provide a log reference. I'm assuming you mean this build:
> 
> http://tinderbox.mozilla.org/showlog.cgi?log=Mozilla-l10n-pl/1252470179.1252470634.21481.gz

Right, that one.

> Last weeks? I do not remember seeing a bug or any message/complaint about it.
> We can't do/check anything if we're not told. Please remember our system is a
> different set of boxes to the MoCo (Firefox) system.

Can you see it now? I can't check everything everyday and provide bug reports about that, day by day, especially if don't have enough info about changes. What's your point here?

Comment 3

[Mark Banner (:standard8)]

(In reply to comment #2)
> > Last weeks? I do not remember seeing a bug or any message/complaint about it.
> > We can't do/check anything if we're not told. Please remember our system is a
> > different set of boxes to the MoCo (Firefox) system.
> 
> Can you see it now? I can't check everything everyday and provide bug reports
> about that, day by day, especially if don't have enough info about changes.
> What's your point here?

My point is that we have no idea what "last weeks" issue was - from your statement I read it as being major and would cause l10n to be late if it happened in the next few days - so you're mentioning about last week's issue, but you've actually said if it is the same or not.

As no-one else has told us either, then we can't correlate the problems and fix them. We're not expecting day by day checks and lots of bugs, but even just mentioning a possible issue on irc (to sipaq or in #maildev) would give us something to look at.

Comment 4

[Philippe M. Chiasson (:gozer)]

(In reply to comment #1)
> (In reply to comment #0)
> 
> It does seem a little late for the builds to start. This feels like our
> builders were too busy with the normal trunk builds to get to the l10n builds,
> but passing to gozer to take a look at it.

Yes, the l10n builds are triggered by the completion of the en-US nightly, and will then be queued (all 54 of them) and picked up by the builders as they come, intermixed with the other kind of builds.

On the linux front, we probably simply don't have enough builders to pick up the additionnal build load sufficiently quickly.

Once beta4 is out (this week), I'll most likely end up at least doubling our Linux build capacity, so that should help a lot.

I am closing this particular bug, as nothing is broken, we just need more capacity. I'll file new bugs for the capacity increase.