473066 - 20090111 Windows Minefield trunk nightly build failed generating the complete .mar file

Status: RESOLVED WORKSFORME

(Release Engineering :: General, defect, P2)

Description

[Bill Gianopoulos [:WG9s]]

Today's (20090111) nightly win32 build failed during the creation of the full .mar file with the error message:

mv: cannot stat`../../dist/firefox.work/output.mar': No such file or directory

Comment 1

[Nick Thomas [:nthomas] (UTC+12)]

This was on moz2-win32-slave11, which luckily didn't clobber the nightly dir on subsequent builds. Slave is disconnected for now.

Comment 2

[Nick Thomas [:nthomas] (UTC+12)]

This is kinda weird and I'm inclined to think it's a one-off glitch (having not seen it before).

* The log for the buildbot step ends
 ignoring remove instruction for directory: searchplugins/
 ignoring remove instruction for directory: extensions/[e-mail]/
 mv: cannot stat `../../dist/firefox.work/output.mar': No such file or directory
 make: Leaving directory `/e/builds/moz2_slave/mozilla-central-win32-nightly/build/obj-firefox/tools/update-packaging'
 program finished with exit code 0
* if you look at a normal log then it's exactly the same except for the cannot stat error
* the Makefile in tools/update-packaging is calling make_full_update.sh, which ends
  # Append remove instructions for any dead files.
  append_remove_instructions "$targetdir" >> $manifest
  
  $BZIP2 -z9 "$manifest" && mv -f "$manifest.bz2" "$manifest"
  
  eval "$MAR -C \"$workdir\" -c output.mar $targetfiles"
  mv -f "$workdir/output.mar" "$archive"

  # cleanup
  rm -fr "$workdir"

* the "ignoring remove instruction" output comes from append_remove_instructions
* output.mar is created by the call to $MAR
* the "cannot stat" comes from the mv call
* the rm should not be starting before the mv has finished, (WHOOP WHOOP WHOOP, LOSS OF CAUSALITY ALERT).

RESOLVED WTF. 

Actually, I just triggered another m-c nightly on the original code revision, and moved on with my day.

Comment 3

[Mike Shaver (:shaver emeritus)]

Do I want to ask what a one-off glitch means?  Non-determinism in the build infrastructure makes me nervous! :)