Closed Bug 849588 (SM2.16.2) Opened 7 years ago Closed 7 years ago
Tracking bug for build and release of Sea
Monkey 2 .16 .2
This is a tracking bug for Build and Release of SeaMonkey 2.16.2 We expect an actual release on Unknown. ----- This is a bug to attempt a rebuild of SM 2.16.1 -- it seems we may have (somehow) regressed nb-NO/l10n with this build. 2.16.0 seems fine.
So, this release will be issued for that single locale only?
(In reply to rsx11m from comment #1) > So, this release will be issued for that single locale only? I'm not sure if that is possible the way our systems are setup, if easily so then yes. If not then I'll investigate the least painful way to upgrade everyone.
(In reply to Justin Wood (:Callek) from comment #2) > (In reply to rsx11m from comment #1) > > So, this release will be issued for that single locale only? > > I'm not sure if that is possible the way our systems are setup, if easily so > then yes. If not then I'll investigate the least painful way to upgrade > everyone. I should add, that depending on what I can find as to a potential reason for the surprise issue in that locale only, I may not even investigate this (if it turns out I have/had a bad system, I'll want to avoid issues for anyone on that system, etc.)
self reflecting note: 2.16.1 nb-NO was built on sea-vm-win32-1 we failed the clobber but built anyway... Other l10n built on that machine: en-GB, pt-PT, and zh-CN -- 2.16.2 nb-NO was still broken, even though it was built on a different machine (which successfully did clobber) It was also broken on linux. Also pt-BR is broken as well. -- I'm going to spin a new build# for 2.16.1, with same csets, for a sanity check that it is Buildbot that broke this.
(In reply to Justin Wood (:Callek) from comment #4) > I'm going to spin a new build# for 2.16.1, with same csets, for a sanity > check that it is Buildbot that broke this. -- 2.16.0 I meant
So, I havent looked yet if updating these users is going to be easy/doable without added pain, but I can say for sure we need this release. it affects all platforms, and each l10n build can be affected at different degrees. Turns out we were not pulling in the l10n-merge stuff (so the cases where we would have used English strings were not actually using said strings), and thus the issues. Fix in http://hg.mozilla.org/build/buildbotcustom/rev/98b5d1f41288
Attachment #723309 - Flags: review?(ewong)
Sooo to recap, because ewong (rightfully) was confused, and to place it somewhere for everyone else: [22:19:59] ewong Callek mind if I asked you some questions about this 2.16.2 bug? I'm a little confused... your latest comment mentions that you're spinning a new build for 2.16.0.. but this is for 2.16.2.. and I dunno if I'm supposed to be confused with this other thing.. the diffs are from changes of 2.15.2-> 2.16.2 [22:20:24] Callek ewong: sure, but let me try to explain [22:20:43] Callek yesterday I got reports of nb-NO being broken... I tested locally and saw it was, in 2.16.1 [22:20:51] Callek tested 2.16.0 release and saw it wasn't broken [22:21:23] Callek then I looked at the repack builder for 2.16.1, saw that it had failed clobber, so I manually clobbered and spun a 2.16.2 build1 [22:21:41] Callek after that I saw that 2.16.2 was still broken, and tonymec also confirmed that it was broken on linux [22:22:09] Callek I didn't see the same clobber issue on linux, nor did I see any changesets that looked responsible (though one did land in packaging on m-c) [22:22:34] Callek so I spun (earlier today-my-time) a 2.16.0 build2 based on the same csets of 2.16.0, just the current buildbot code. [22:22:39] Callek that build2 ALSO failed [22:22:57] Callek so, now that we have this buildbotcustom fix in place, and after our investigation, we're back up to 2.16.2 build2 [22:23:04] Callek with the proper previous-build
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.