On Wed, 2007-07-04 at 00:55 -0700, bugzilla-daemon at np.grommit.com wrote: > If $BRINGOVER_WS is set, $CODEMGR_WS is not (ie, a full bringover + build), > nightly will bail out if $BRINGOVER_WS is not on the local filesystem, as it > attempts to find usr/src/Makefile there for informational purposes: > > Unable to find "Makefile" in ssh://<hostname>//builds/onnv-clone/usr/src or > /builds/work/onnv-sccs/this-wont-work/usr/src. > > This happens as it's trying to ouput tools versions, very early on, which it > does before it brings over.
there's a bunch of subtlety baked in there; see in particular: 6266590 nightly misbehaving when kicked-off from empty ws 6232357 nightly can run through the air for hours before looking down I suspect that fixing this without causing a regression on either of these bugs may require reordering the tool version check to happen after the clobber and the bringover steps. (clobber needs to run with the "old" makefiles since otherwise you won't clean up a component that has just been deleted).
