Canmove, confirm
6,439
edits
Changes
no edit summary
Because of rebuilding tag instead of re-doing sendchanges, all repacks are failing because "script_repo_revision" isn't set. These can be fixed by forcing the failed builders and setting a "script_repo_revision" property to the release tag (eg, FIREFOX_18_0_RELEASE). I've done this for all failed repacks that I've seen. (Though, some have additional problems, see below for details).
=== Win32 build failed ===
Win32 build failed with what looks like a path-length-too-long problem ("bad file number"). I couldn't figure out what to shorten in the directory path that didn't seem incredibly risky to do. Not sure what to do here. FIXMEThe nightly build dir has 13 chars in it ("tb-c-esr17-w32") and the release one has 21 ("tb-rel-c-esr17-w32-bld"). Attempt #1: Shorten "esr" to "e". Landed this patch: https://hg.mozilla.org/build/buildbotcustom/graph, reconfiged the build masters, and rebuilt the win32_build. Trying this first because I'm scared of wide sweeping changes if I touch the tb- prefix or other parts of the path.
=== Linux repacks failed ===
Linux repacks failing with "cannot create executable" during configure. I suspect this is related to mock, wasn't able to look into it. FIXME
