443397 - Thunderbird Mac tinderbox not pulling the latest build-seamonkey-util.pl

Status: RESOLVED FIXED

(Release Engineering :: General, defect)

Description

[Mark Banner (:standard8)]

In trying to fix bustages reported on "MacOSX Darwin 8.8.4 bm-xserve07 Dep Universal Nightly" from bug 397621, I checked in a change to build-seamonkey-util.pl today (with r=reed).

The tinderbox cycled, but the error remained. I thought tinderboxes were meant to automatically pick up build-seamonkey-util.pl changes?

As it happened after the second cycle as well I'm fairly sure its not picking up the changes.

Not sure if our other two tinderboxes have the same problem or not.

Comment 1

[Mark Banner (:standard8)]

Please can someone take a look at this? It has been a week since I filed it, and I would like to try and get the rest of the blocking bug fixed asap.

Comment 2

[Armen [:armenzg]]

(In reply to comment #0)
> In trying to fix bustages reported on "MacOSX Darwin 8.8.4 bm-xserve07 Dep
> Universal Nightly" from bug 397621, I checked in a change to
> build-seamonkey-util.pl today (with r=reed).
> 
Which patch do you refer to?

> The tinderbox cycled, but the error remained. I thought tinderboxes were meant
> to automatically pick up build-seamonkey-util.pl changes?
> 
Out of my little experience and this is out of my sixth sense, I would say that it does not get updated and if it does it might be through a crontab. 

I can let you know that sticky tag being used is RELEASE_AUTOMATION_M9 and it is up to date from what I can see

Comment 3

[Mark Banner (:standard8)]

(In reply to comment #2)
> (In reply to comment #0)
> > In trying to fix bustages reported on "MacOSX Darwin 8.8.4 bm-xserve07 Dep
> > Universal Nightly" from bug 397621, I checked in a change to
> > build-seamonkey-util.pl today (with r=reed).
> > 
> Which patch do you refer to?

bug 397621 attachment 327945 [details] [diff] [review].

This link shows the checkins I tried:

http://bonsai.mozilla.org/cvsquery.cgi?treeid=default&module=all&branch=HEAD&branchtype=match&dir=&file=&filetype=match&who=bugzilla%25standard8.plus.com&whotype=match&sortby=Date&hours=2&date=explicit&mindate=2008-07-03+02%3A49&maxdate=2008-07-03+01%3A25&cvsroot=%2Fcvsroot

> > The tinderbox cycled, but the error remained. I thought tinderboxes were meant
> > to automatically pick up build-seamonkey-util.pl changes?
> > 
> Out of my little experience and this is out of my sixth sense, I would say that
> it does not get updated and if it does it might be through a crontab. 
> 
> I can let you know that sticky tag being used is RELEASE_AUTOMATION_M9 and it
> is up to date from what I can see

This definitely explains why it wasn't picked up.

cvs status -v build-seamonkey-util.pl tells me there's M9_1, M9_2 and M10 at least.

I believe that when I've checked in changes to build-seamonkey-util.pl in the past I've been told that the MoCo tinderboxes will automatically pick up the changes, i.e. implying that they follow HEAD. Though I could be wrong.

It is interesting that the RELEASE_AUTOMATION_M9 tag was set and used for TB 3.0a1 which I'm 90% sure was done using the trunk tinderboxes that we're having problems with (see http://wiki.mozilla.org/Thunderbird3.0a1:BuildNotes#Build_1).


So I believe the questions are now:

1) Are the tinderboxes meant to track HEAD or a tag for the tinderbox tools?

if HEAD then:

2a) Can someone switch all three Thunderbird tinderboxes back to HEAD please?

if a tag:

2b) Can someone create a new tag and update the Thunderbird tinderboxes?
2c) How should this process normally work and where is it documented? (if it isn't then I think it should be).

Comment 4

[Nick Thomas [:nthomas] (UTC+12)]

You're correct that this is a leftover from the 3.0a1 release, the nightly boxes should track HEAD.

Comment 5

[Nick Thomas [:nthomas] (UTC+12)]

Linux and Windows updated to HEAD. Armen, are you working on the mac one ?

Comment 6

[Armen [:armenzg]]

Yes, I am.

Updated to HEAD

Comment 7

[Armen [:armenzg]]

fts_read problems - I have filed bug 444949

Comment 8

[Nick Thomas [:nthomas] (UTC+12)]

All done here.