Closed
Bug 1175735
Opened 9 years ago
Closed 9 years ago
beta builds breaking in Files section of Lightning moz.build
Categories
(Calendar :: Build Config, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: rkent, Unassigned)
References
Details
+++ This bug was initially created as a clone of Bug #1139679 +++
Beta builds breaking (also locally for me) with the Files definition. See log from https://treeherder.mozilla.org/logviewer.html#?job_id=3076&repo=comm-beta:
Traceback (most recent call last):
File "./config.status", line 977, in <module>
config_status(**args)
File "/builds/slave/tb-c-beta-m64-0000000000000000/build/mozilla/python/mozbuild/mozbuild/config_status.py", line 149, in config_status
summary = the_backend.consume(definitions)
File "/builds/slave/tb-c-beta-m64-0000000000000000/build/mozilla/python/mozbuild/mozbuild/backend/base.py", line 180, in consume
for obj in objs:
File "/builds/slave/tb-c-beta-m64-0000000000000000/build/mozilla/python/mozbuild/mozbuild/frontend/emitter.py", line 137, in emit
for out in output:
File "/builds/slave/tb-c-beta-m64-0000000000000000/build/mozilla/python/mozbuild/mozbuild/frontend/reader.py", line 909, in read_mozbuild
raise bre
mozbuild.frontend.reader.BuildReaderError:
==============================
ERROR PROCESSING MOZBUILD FILE
==============================
The error occurred while processing the following file:
/builds/slave/tb-c-beta-m64-0000000000000000/build/calendar/lightning/moz.build
The error was triggered on line 34 of this file:
with Files('**'):
An error was encountered as part of executing the file itself. The error appears to be the fault of the script.
The error as reported by Python is:
["NameError: name 'Files' is not defined\n"]
*** Fix above errors and then restart with "make -f client.mk build"
make[3]: *** [configure] Error 1
make[2]: *** [/builds/slave/tb-c-beta-m64-0000000000000000/build/objdir-tb/i386/config.status] Error 2
make[1]: *** [build] Error 2
make: *** [build] Error 2
Reporter | ||
Comment 1•9 years ago
|
||
OK sorry, this is a result of the mozilla repo not getting updated from a previous branch.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•