I guess something changed in the Buildbot environment? Logs at [1] > diff: target/bin: No such file or directory > FAIL: unknown error from diff: 2 > FAIL: [56.0 en-ZA complete] check_updates returned unknown error for WINNT_x86-msvc-x86 downloads/Firefox Setup 56.0b11.exe vs. downloads/Firefox Setup 57.0b1.exe: 3 [1] https://archive.mozilla.org/pub/devedition/tinderbox-builds/mozilla-beta-win32/release-mozilla-beta_devedition_win32_update_verify-bm94-build1-build22.txt.gz

The spot instances for these have gone away so I'm rerunning https://tools.taskcluster.net/groups/SccqGTzATvqPXaVMW4LjJQ/tasks/HPwL6Hk4SzmPbdlr7PSFVg/details and debugging

This is not an intermittent isssue, it occurs with multiple retries. I haven't been able to ssh or connect to a spot instance to see the error on a 2008-spot machine. I don't know what is wrong with my credentials. I'll ask the buildduty folks on Monday. (Since devedition isn't going to be released until next week anyways my understanding is that this bug is not urgent) I compared the revisions of m-b, tools, puppet and buildbot configs to try to determine if there are changes that would cause this and haven't found anything yet.

For some reason we're hitting this line in unpack.sh: https://hg.mozilla.org/build/tools/file/tip/release/common/unpack.sh#l67 You can see in the log some messages about failing to unzip xpi files.

It looks like the l10n repacks on windows are using 'firefox' as the top-level directory in the installer instead of 'core'. http://releases.mozilla.com/pub/devedition/candidates/57.0b1-candidates/build2/win64/en-US/Firefox%20Setup%2057.0b1.exe has 'core' in the top-level http://releases.mozilla.com/pub/devedition/candidates/57.0b1-candidates/build2/win64/ach/Firefox%20Setup%2057.0b1.exe has 'firefox'