Closed Bug 590635 Opened 14 years ago Closed 14 years ago

SeaMonkey 2.1b1pre French and Russian builds are missing

Categories

(SeaMonkey :: Release Engineering, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED
seamonkey2.1b1

People

(Reporter: unghost, Assigned: kairo)

Details

SeaMonkey 2.1b1pre French and Russian builds are missing in http://ftp.mozilla.org/pub/mozilla.org/seamonkey/nightly/latest-comm-central-trunk-l10n/ On http://tinderbox.mozilla.org/showbuilds.cgi?tree=Mozilla-l10n-fr and http://tinderbox.mozilla.org/showbuilds.cgi?tree=Mozilla-l10n-ru SeaMonkey trunk build machines are on fire. From irc chat with Kairo: KaiRo> Unghost: looks like there's an error because it doesn't find the complete mar of the previous nightly, please file a bug, this looks like a bug in our buildbot scripts
The latest buildbotcustom code makes builds go orange if a previous complete mar can't be found, but still publishes the builds that just completed. Is SeaMonkey up to date ?
(In reply to comment #1) > The latest buildbotcustom code makes builds go orange if a previous complete > mar can't be found, but still publishes the builds that just completed. Is > SeaMonkey up to date ? I just updated buildbotcustom last weekend, and again today, so it should be current. I drew that conclusion because the logs show looking for a complete MAR as the last executed step and I couldn't see an obvious error elsewhere. I haven't dug into buildbot though.
Assignee: nobody → kairo
Product: mozilla.org → SeaMonkey
QA Contact: release → release
Version: other → unspecified
buildbot status of such a build is: failed get_previous_mar_filename build step stdio: bash -c ssh -l seabld -i ~/.ssh/seabld_dsa stage.mozilla.org ls -1t /pub/mozilla.org/seamonkey/nightly/latest-comm-central-trunk-l10n | grep .fr.linux-i686.complete.mar in dir /builds/slave/comm-central-trunk-linux-l10n-nightly/build (timeout 1200 secs) watching logfiles {} argv: ['bash', '-c', 'ssh -l seabld -i ~/.ssh/seabld_dsa stage.mozilla.org ls -1t /pub/mozilla.org/seamonkey/nightly/latest-comm-central-trunk-l10n | grep .fr.linux-i686.complete.mar'] environment: CVS_RSH=ssh G_BROKEN_FILENAMES=1 HISTSIZE=1000 HOME=/home/seabld HOSTNAME=cn-sea-qm-centos5-01 INPUTRC=/etc/inputrc LANG=en_US.UTF-8 LESSOPEN=|/usr/bin/lesspipe.sh %s LOGNAME=seabld LS_COLORS=no=00:fi=00:di=01;34:ln=01;36:pi=40;33:so=01;35:bd=40;33;01:cd=40;33;01:or=01;05;37;41:mi=01;05;37;41:ex=01;32:*.cmd=01;32:*.exe=01;32:*.com=01;32:*.btm=01;32:*.bat=01;32:*.sh=01;32:*.csh=01;32:*.tar=01;31:*.tgz=01;31:*.arj=01;31:*.taz=01;31:*.lzh=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.gz=01;31:*.bz2=01;31:*.bz=01;31:*.tz=01;31:*.rpm=01;31:*.cpio=01;31:*.jpg=01;35:*.gif=01;35:*.bmp=01;35:*.xbm=01;35:*.xpm=01;35:*.png=01;35:*.tif=01;35: MAIL=/var/spool/mail/seabld PATH=/opt/local/bin:/tools/python/bin:/tools/buildbot/bin:/tools/python/bin:/usr/kerberos/bin:/usr/local/bin:/bin:/usr/bin:/home/seabld/bin PWD=/builds/slave/comm-central-trunk-linux-l10n-nightly/build SHELL=/bin/bash SHLVL=1 SSH_ASKPASS=/usr/libexec/openssh/gnome-ssh-askpass TERM=linux USER=seabld _=/tools/buildbot/bin/buildbot closing stdin using PTY: True program finished with exit code 1 elapsedTime=2.722522
OK, so bug 573999 would fix this, but it applies on buildbot 0.8 only, and we're still running 0.7 because release runs haven't been tested on 0.8 yet.
Coop, I heard you have a trick to fake the complete MARs for a run there so this passes? Can you tell me about it?
OK, coop said he used to just copy over an en-US MAR and that would do the trick, I'll look into that. BTW, this bug now happens for win32 on almost all locales.
(In reply to comment #6) > OK, coop said he used to just copy over an en-US MAR and that would do the > trick, I'll look into that. Yes, you're not trying to create a legit update, just work around the issue, so this should get you unstuck.
I copied over MARs from all locales and all 3 platforms yesterday for all those that were missing (which were way more than fr and ru, BTW), and most of them are complete now (as long as they build, some don't - probably due to chatzilla or venkman strings). Some win32 repacks are still spinning, but things look good now.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Target Milestone: --- → seamonkey2.1b1
You need to log in before you can comment on or make changes to this bug.