Closed Bug 348575 Opened 18 years ago Closed 18 years ago

No GTK2 Seamonkey builds since August 9th

Categories

(SeaMonkey :: Installer, defect)

x86
Linux
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: bzbarsky, Assigned: ajschult784)

Details

(Keywords: fixed-seamonkey1.0.6, fixed-seamonkey1.1b)

Attachments

(3 files, 1 obsolete file)

The last GTK2 Seamonkey build on the FTP site is 2006-08-09-01.  After that, there are two days of no -01 directory, followed by several days of that directory existing but being empty.

Looking at tinderbox, lhasa is building.  So the problem is presumably getting the builds pushed to the FTP site?

In any case, this is blocking me hunting down some Gecko regressions right now.  :(
lhasa's build log includes

cp /builds/tinderbox/SeaMonkey-Release/Linux_2.4.20-28.8_Depend/mozilla/installer/../dist/*.tar.* /builds/tinderbox/SeaMonkey-Release/Linux_2.4.20-28.8_Depend/mozilla/installer/2006-08-14-13-trunk/
cp: cannot create regular file `/builds/tinderbox/SeaMonkey-Release/Linux_2.4.20-28.8_Depend/mozilla/installer/2006-08-14-13-trunk/seamonkey-1.5a.en-US.linux-i686.tar.bz2': No such file or directory
Assignee: build → ccooper
Status: NEW → ASSIGNED
I've reverted the tinderbox patches from 2006/07/09 (http://bonsai.mozilla.org/cvsquery.cgi?treeid=default&module=all&branch=HEAD&branchtype=match&dir=&file=&filetype=match&who=preed&whotype=regexp&sortby=Date&hours=2&date=explicit&mindate=2006-08-09+12%3A00%3A00&maxdate=2006-08-09+13%3A00%3A00&cvsroot=%2Fcvsroot). Tinderbox has been clobbered and restarted.

Nothing obvious leaps out at me from those patches, but that patch is from the exact timeframe when lhasa failed. There is probably a subtle directory creation/naming difference in the script that we are missing.
(In reply to comment #2)
> I've reverted the tinderbox patches from 2006/07/09

Er, 2006/08/09. The bonsai query is correct though.
On my "hoshi" SeaMonkey Linuc tinderbox, I have this workaround in place. I'm not sure why this is needed, as before the if block, $stagedir should be created on all platforms, but somehow it sometimes fails on Linux, though it works perfectly on Windows and Mac.
Oh!  I have that patch too on nye.  :)

The installer packaging nukes the directory.
Assignee: ccooper → rhelmer
Attachment #233891 - Attachment is obsolete: true
This is temporary, until we figure out why this directory is getting blown away (presumably by the packaging process).
Checking in post-mozilla-rel.pl;
/cvsroot/mozilla/tools/tinderbox/post-mozilla-rel.pl,v  <--  post-mozilla-rel.plnew revision: 1.104; previous revision: 1.103
done


Let's leave this open until we have a better solution.
So... the tbox scripts
1. create [tbox_path]/mozilla/installer/2006-08-15-15-trunk
2. create [tbox_path]/mozilla/installer
3. invoke installer packaging, which puts the results in [tbox_path]/mozilla/installer
4. expects the directory created in #1 to exist.

http://bonsai.mozilla.org/cvsblame.cgi?file=mozilla/tools/tinderbox/post-mozilla-rel.pl&rev=1.103&mark=240,254,266,319,1274#230
(stagedir is made to be a subdirectory of package_location on line 1274)

The difference on windows seems to be that it seems to use (and nuke) dist/stage/mozilla/ to stage files for the installer (outside of dist/install/ where it seems to put the final packages).  The toolkit packaging is similar.

I'll attach a patch that should make tbox happy.
Attached patch patchSplinter Review
just nuke the stuff in installer/
(In reply to comment #10)
> Created an attachment (id=233935) [edit]
> patch
> 
> just nuke the stuff in installer/
> 

aj, can you land this patch? feel free to remove the hacky workaround patch too, or I will do it after you land.
someone needs to pretend to know this code first  :)
Assignee: rhelmer → ajschult
Status: ASSIGNED → NEW
Component: Build & Release → Installer
Product: mozilla.org → Mozilla Application Suite
Version: other → Trunk
Attachment #233935 - Flags: review?(kairo)
Comment on attachment 233935 [details] [diff] [review]
patch

OK, I'll pretend to know the code then ;-)
r=me, looks like we're cleaning up everything the installer build process needs.

What we're not doing now though is cleaning up the packaging directory tinderbox uses inside installer/ so we'll pile up those directories in installer/ which isn't good.

Currently, the call to packit() in http://lxr.mozilla.org/mozilla/source/tools/tinderbox/post-mozilla-rel.pl#1283
causes $local_build_dir to be created in that function (through the previously wiped away command and our dirty workaround).
After http://lxr.mozilla.org/mozilla/source/tools/tinderbox/post-mozilla-rel.pl#1326 copies that to a better location, I guess we could clean that up, so installer/ has no remnants of tinderbox's work.
Attachment #233935 - Flags: review?(kairo) → review+
> What we're not doing now though is cleaning up the packaging directory
> tinderbox uses inside installer/

Right.  Windows doesn't do this either.  I assumed that the tbox scripts would take care of whatever garbage they create.  Do these installer packages just build up on the windows tboxes?
This implements what Robert mentioned in comment 13
Attachment #236031 - Flags: review?(rhelmer)
Attachment #236031 - Flags: review?(rhelmer) → review+
OK, I landed both patches.

KaiRo, should we land the packaging script fix on the branch?  I guess if you leave the hack in it won't matter.
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
Andrew, I think a branch landing would probably be nice, esp. as this code is only used in SeaMonkey nowadays anyways and we haven't shipped a beta yet so we have no freeze in SeaMonkey-specific code at the moment.
Attachment #233935 - Flags: approval-seamonkey1.1b+
Comment on attachment 233935 [details] [diff] [review]
patch

This is a small, Linux installer only fix, very low risk, I think it would be good to take it on 1.8.0 as well, so a first a=me for SeaMonkey 1.0.6 (marking this with the 1.0.5 flag request as we don't have a 1.0.6 one yet), need another Council member to set to +
Attachment #233935 - Flags: approval-seamonkey1.0.5?
Comment on attachment 233935 [details] [diff] [review]
patch

a=biesi
Attachment #233935 - Flags: approval-seamonkey1.0.5? → approval-seamonkey1.0.5+
we need new keywords too...
Keywords: fixed1.8.0.8
Attachment #233935 - Flags: approval-seamonkey1.0.5+ → approval-seamonkey1.0.6+
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: