Closed
Bug 1008596
Opened 11 years ago
Closed 11 years ago
No SeaMonkey 2.28a2 nightly aurora builds, likely due to wrong relbranches in client.py configuration
Categories
(SeaMonkey :: Build Config, defect)
Tracking
(seamonkey2.28 verified, seamonkey2.29 fixed)
RESOLVED
FIXED
People
(Reporter: rsx11m.pub, Assigned: iannbugzilla)
Details
(Keywords: verifyme)
Attachments
(2 files)
1.12 KB,
patch
|
mcsmurf
:
review+
philip.chee
:
approval-comm-aurora+
|
Details | Diff | Splinter Review |
1.18 KB,
patch
|
mcsmurf
:
review+
|
Details | Diff | Splinter Review |
The following issue is reported in both Windows and Mac OSX build logs (and likely would be seen on Linux if bug 983536 were fixed), thus no 2.28a2 builds are generated. Judging from how the bug manifests itself, this seems to be the same issue as bug 985964 which occurred after the last merge:
> updating cache /e/builds/slave/c-aurora-w32-ntly/build/objdir/config.cache
> creating ./config.status
> Reticulating splines...
> Traceback (most recent call last):
> File "./config.status", line 908, in <module>
> config_status(**args)
> File "e:\builds\slave\c-aurora-w32-ntly\build\mozilla\python\mozbuild\mozbuild\config_status.py", line 148, in config_status
> summary = the_backend.consume(definitions)
> File "e:\builds\slave\c-aurora-w32-ntly\build\mozilla\python\mozbuild\mozbuild\backend\base.py", line 186, in consume
> for obj in objs:
> File "e:\builds\slave\c-aurora-w32-ntly\build\mozilla\python\mozbuild\mozbuild\frontend\emitter.py", line 106, in emit
> objs = list(self.emit_from_sandbox(out))
> File "e:\builds\slave\c-aurora-w32-ntly\build\mozilla\python\mozbuild\mozbuild\frontend\emitter.py", line 429, in emit_from_sandbox
> sandbox['SRCDIR'])
> mozbuild.frontend.reader.SandboxValidationError: A jar.mn exists in e:/builds/slave/c-aurora-w32-ntly/build/mozilla/extensions/venkman/resources but it is not referenced in the corresponding moz.build file. Please define JAR_MANIFESTS in the moz.build file.
> *** Fix above errors and then restart with "D:/mozilla-build/python27/python2.7.exe e:/builds/slave/c-aurora-w32-ntly/build/mozilla/build/pymake/pymake/../make.py -f client.mk build"
The following is seen in the Windows logs only:
> e:\builds\slave\c-aurora-w32-ntly\build\client.mk:350:0: command 'cd objdir && MAKE="D:/mozilla-build/python27/python2.7.exe e:/builds/slave/c-aurora-w32-ntly/build/mozilla/build/pymake/pymake/../make.py" e:/builds/slave/c-aurora-w32-ntly/build/configure \
> || ( echo "*** Fix above errors and then restart with\
> \"D:/mozilla-build/python27/python2.7.exe e:/builds/slave/c-aurora-w32-ntly/build/mozilla/build/pymake/pymake/../make.py -f client.mk build\"" && exit 1 )' failed, return code 1
> e:\builds\slave\c-aurora-w32-ntly\build\client.mk:362:0: command 'D:/mozilla-build/python27/python2.7.exe e:/builds/slave/c-aurora-w32-ntly/build/mozilla/build/pymake/pymake/../make.py -f e:/builds/slave/c-aurora-w32-ntly/build/client.mk configure' failed, return code 2
> configure: error: e:/builds/slave/c-aurora-w32-ntly/build/mozilla/configure failed for mozilla
> Traceback (most recent call last):
> File "e:/builds/slave/c-aurora-w32-ntly/build/build/pymake/make.py", line 35, in <module>
> main(sys.argv[1:])
> File "e:/builds/slave/c-aurora-w32-ntly/build/build/pymake/make.py", line 32, in main
> subprocess.check_call([sys.executable, PYMAKE] + args)
> File "D:\mozilla-build\python27\lib\subprocess.py", line 511, in check_call
> raise CalledProcessError(retcode, cmd)
> subprocess.CalledProcessError: Command '['D:\\mozilla-build\\python27\\python2.7.exe', 'e:\\builds\\slave\\c-aurora-w32-ntly\\build\\mozilla\\build\\pymake\\make.py', '-f', 'client.mk', 'build', 'MOZ_BUILD_DATE=20140510013001']' returned non-zero exit status 2
> program finished with exit code 1
(Quoting rsx11m from bug 985964 comment #7)
> So, this will have to be done after each merge now ...
... apparently yes, at least for this cycle.
> or is there some way to automate it?
Any ideas?
http://hg.mozilla.org/releases/comm-aurora/file/ebcaac24ae6e/client.py [AURORA_30_END] uses SEA2_26_RELBRANCH, yet http://hg.mozilla.org/releases/comm-aurora/file/6d6550f3e91a/client.py [AURORA_BASE_20140429] switched that back to SEA2_25_RELBRANCH. Why does that happen?
Anything that needs to be changed in the comm-central client.py definitions? Current definitions http://hg.mozilla.org/comm-central/file/27968692278f/client.py there show SEA2_25_RELBRANCH commented out. Would updating it there to 2_26 prevent flipping it back at the time of the next merge?
Change to SEA2_26_RELBRANCH
Change to SEA2_26_RELBRANCH
Attachment #8420712 -
Flags: review?(neil)
Comment on attachment 8420711 [details] [diff] [review]
Patch for aurora [Checked in: Comment 6]
[Approval Request Comment]
Regression caused by (bug #):
User impact if declined: aurora cannot be built
Testing completed (on m-c, etc.): local tree
Risk to taking this patch (and alternatives if risky): none
String changes made by this patch: none
Attachment #8420711 -
Flags: approval-comm-aurora?
Comment on attachment 8420711 [details] [diff] [review]
Patch for aurora [Checked in: Comment 6]
https://hg.mozilla.org/releases/comm-aurora/rev/525c829ab5fb
Checked in as a bustage fix, any review comments can be fixed as a followup.
Attachment #8420711 -
Attachment description: Patch for aurora → Patch for aurora [Checked in: Comment 6]
The Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 SeaMonkey/2.28a2 nightly build looks good to me; I don't see any Mac OSX builds yet, but the acute bustage seems to be fixed (again).
Mac OSX builds are done now as well, so verified fixed as far as current aurora is concerned.
status-seamonkey2.28:
--- → verified
![]() |
||
Comment 9•11 years ago
|
||
Comment on attachment 8420711 [details] [diff] [review]
Patch for aurora [Checked in: Comment 6]
rs=aurora bustage fix
Attachment #8420711 -
Flags: approval-comm-aurora? → approval-comm-aurora+
Comment 10•11 years ago
|
||
For reference: Chatzilla etc. branches were created here https://hg.mozilla.org/chatzilla/rev/2a50fb6c1691
Comment 11•11 years ago
|
||
Comment on attachment 8420711 [details] [diff] [review]
Patch for aurora [Checked in: Comment 6]
Looks fine to me, stealing review.
Attachment #8420711 -
Flags: review?(neil) → review+
Comment 12•11 years ago
|
||
Comment on attachment 8420712 [details] [diff] [review]
Patch for trunk [Checked in trunk: Comment 13]
This is fine, too.
Attachment #8420712 -
Flags: review?(neil) → review+
Assignee | ||
Comment 13•11 years ago
|
||
Comment on attachment 8420712 [details] [diff] [review]
Patch for trunk [Checked in trunk: Comment 13]
https://hg.mozilla.org/comm-central/rev/68da72a28bb3
Attachment #8420712 -
Attachment description: Patch for trunk → Patch for trunk [Checked in trunk: Comment 13]
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
![]() |
Reporter | |
Comment 14•11 years ago
|
||
Needs to be verified for 2.29a2 after the next merge scheduled for June 10.
status-seamonkey2.29:
--- → fixed
Keywords: verifyme
You need to log in
before you can comment on or make changes to this bug.
Description
•