This seems to be the result of a change in the way that MH looks for configs.

Something has changed between 0.0.14 and 0.0.15, that makes custom configs fail: http://i.imgur.com/VkNlOZV.gif Note, it's not a mozharness change (see the gif above).

It doesn't look like there ever was a 0.0.14 in-tree, and I may not have been very good about bumping VERSION when actually landing things, and about ensuring that the image with tag $VERSION matches what's in-tree with that VERSION. I just built and pushed 0.0.16 from 6256ee8a3344 (my latest push to inbound). Give that a try, and if it works we can push a VERSION bump to 0.0.16 and call it good. I'll try to be more careful from here on out :)

I changed testing/docker/desktop-build/VERSION to 0.0.16 and still hit this error: https://treeherder.mozilla.org/#/jobs?repo=try&revision=21a32469860a&exclusion_profile=false&filter-searchStr=tc Adding MOZ_AUTOMATION_UPLOAD: 0 seems to have fixed the other bug though.

Sorry, I should have seen this the first time -- we now use --no-sendchange to disable sendchange, so it's no longer required in the build task.

Bug 1171390: bump desktop-build VERSION; r=ahal

Bug 1171390: don't use disable_sendchange.py; r=ahal This file has been removed and is no longer necessary, as build.sh passes --no-sendchange to mozharness.

Comment on attachment 8615346 [details] MozReview Request: Bug 1171390: don't use disable_sendchange.py; r=ahal https://reviewboard.mozilla.org/r/10239/#review8957 Ship It!

Comment on attachment 8615345 [details] MozReview Request: Bug 1171390: bump desktop-build VERSION; r=ahal https://reviewboard.mozilla.org/r/10237/#review8959 Ship It!

https://hg.mozilla.org/integration/mozilla-inbound/rev/1a3a686db65e https://hg.mozilla.org/integration/mozilla-inbound/rev/2a94367985a4

https://hg.mozilla.org/mozilla-central/rev/1a3a686db65e https://hg.mozilla.org/mozilla-central/rev/2a94367985a4