I'm down to https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=db003dd8a348&tochange=2134cb641802 which makes no sense. FWIW, I'm on an intel mac, and :Mossop has reported he's had no issues building from more recent csets (on a silicon mac, I _think_). It's also worth noting that the tests archives do appear to have the relevant file: ``` > tar -tf ~/.mozbuild/package-frontend/6ec6ec0936392602-target.common.tests.tar.gz | grep updater- updater-dep/updater-dep xpcshell/tests/toolkit/mozapps/update/tests/updater-xpcshell ``` so I don't understand why it doesn't get staged into `objdir/_tests`. (I checked, the file is really not there.)
Bug 1748829 Comment 2 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
I'm down to https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=db003dd8a348&tochange=2134cb641802 as a regressing range, which makes no sense. 2 out of the 3 csets have been backed out and the other is a change to some stuff in the binary but shouldn't affect the build system at all. FWIW, I'm on an intel mac, and :Mossop has reported he's had no issues building from more recent csets (on a silicon mac, I _think_). It's also worth noting that the tests archives do appear to have the relevant file: ``` > tar -tf ~/.mozbuild/package-frontend/6ec6ec0936392602-target.common.tests.tar.gz | grep updater- updater-dep/updater-dep xpcshell/tests/toolkit/mozapps/update/tests/updater-xpcshell ``` so I don't understand why it doesn't get staged into `objdir/_tests`. (I checked, the file is really not there.)