Build bustage all platforms on 2017-06-08

RESOLVED FIXED in Thunderbird 55.0


Build Config
11 months ago
11 months ago


(Reporter: Jorg K (GMT+1), Unassigned)


Thunderbird 55.0

Firefox Tracking Flags

(Not tracked)




11 months ago
All platforms fail, but the errors are different:

Linux 64:
make[5]: *** [mozmill-virtualenv] Error 1

../../../config/nsinstall: cannot access /builds/slave/tb-c-cen-l64-00000000000000000/build/mozilla/python/virtualenv: No such file or directory
make[5]: *** [mozmill-virtualenv] Error 1

ImportError: No module named which
make[2]: *** [backend.RecursiveMakeBackend] Error 1
make[1]: *** [build] Error 2
make: *** [build] Error 2
program finished with exit code 2

IOError: [Errno 2] No such file or directory: u'c:\\builds\\moz2_slave\\tb-c-cen-w32-00000000000000000\\build\\mozilla\\python\\virtualenv' 

Maybe a buildbot change. M-C regression interval:

Last good: 7efda263a842
First bad: 6491fb29e7fc


The only build related bug in the range is bug 1356952. But that only changed files under /taskcluster. Oh, there's also bug 1370421.

Do putting NI for some people who might know something about this.

Off-topic: The TB Council is currently conducting job interviews for a build/release engineer. So hopefully pretty soon we'll know who to call if something like this happens.
Flags: needinfo?(mshal)
Flags: needinfo?(mh+mozilla)
Flags: needinfo?(gps)
Flags: needinfo?(ewong)

Comment 1

11 months ago
Richard reports a failing local build:

 0:05.98 ImportError: No module named which
 0:05.98 z:/Mozilla/comm-central/mozilla/build/
recipe for target 'backend.RecursiveMakeBackend' failed
 0:05.98 mozmake.EXE[1]: *** [backend.RecursiveMakeBackend] Error 1
 0:05.99 recipe for target 'build' failed
 0:05.99 mozmake.EXE: *** [build] Error 2
 0:06.01 266 compiler warnings present.

Comment 2

11 months ago
Richard reckons it's from bug 1346025.

Comment 3

11 months ago
Hmm, I did a clobber on treeherder C-C and retriggered a job which has been running for ten minutes now where the failed job took two minutes. So perhaps a false alarm?

Comment 4

11 months ago
Yes, a clobber may be needed. Also, audit your code for references to "sys.path" and "python/" and adjust moved paths accordingly.
Flags: needinfo?(mshal)
Flags: needinfo?(mh+mozilla)
Flags: needinfo?(gps)

Comment 5

11 months ago
We have a few usages of sys.path, but perhaps more importantly:
22 $(INSTALL) $(topsrcdir)/mozilla/python/virtualenv $(_DEST_DIR)/resources/

That looks like the error from comment #0:
cannot access /builds/slave/tb-c-cen-l64-00000000000000000/build/mozilla/python/virtualenv

So that's now in /third_party/python.
Flags: needinfo?(ewong)

Comment 7

11 months ago
That did the trick. |hg qfinish -a| ate my patch, so no attachment here ;-)

One liner:
-	$(INSTALL) $(topsrcdir)/mozilla/python/virtualenv $(_DEST_DIR)/resources/
+	$(INSTALL) $(topsrcdir)/mozilla/third_party/python/virtualenv $(_DEST_DIR)/resources/
Last Resolved: 11 months ago
Resolution: --- → FIXED
Target Milestone: --- → Thunderbird 55.0


11 months ago
Duplicate of this bug: 1371377

Comment 9

11 months ago
This patch is in C-C tree, correct?
I updated local C-C tree by |make -f checkout| but it did not get fetched. Oh well.


Comment 10

11 months ago
Then you need to clean your local repository: Do "hg out" and "hg strip" and "hg pull" and "hg up -C default".

Comment 11

11 months ago
It seems that there is a slight delay between the patch being submitted and the (outward) server from which I pick up
the recent C-C tree.
I did the following as you suggested (I did not understand what the commands do, but after seeing the messages I think I do now.)

--- begin quote ---
ishikawa@ip030:/NREF-COMM-CENTRAL/comm-central$ hg out
comparing with
real URL is
searching for changes
no changes found
ishikawa@ip030:/NREF-COMM-CENTRAL/comm-central$ hg strip
abort: empty revision set
ishikawa@ip030:/NREF-COMM-CENTRAL/comm-central$ hg pull
pulling from
real URL is
searching for changes
no changes found
ishikawa@ip030:/NREF-COMM-CENTRAL/comm-central$ hg up -C default
0 files updated, 0 files merged, 0 files removed, 0 files unresolved

--- end quote ---

Oh well, maybe it would work now ...
You need to log in before you can comment on or make changes to this bug.