mach artifact install fails with "No such file or directory 'objdir-frontend/dist/bin/plugin-container'"

VERIFIED FIXED in Firefox 53



Build Config
2 years ago
11 months ago


(Reporter: johannh, Assigned: standard8)


(Blocks: 1 bug)

Dependency tree / graph

Firefox Tracking Flags

(firefox53 fixed)


MozReview Requests


Submitter Diff Changes Open Issues Last Updated
Error loading review requests:


(1 attachment)



2 years ago
Full output

tl;dr my mach build command (after clobber) fails to run because it can not find "objdir-frontend/dist/bin/plugin-container".


2 years ago
Blocks: 901840
No longer blocks: 1277841
Blocks: 1114647
It's weird, but after trying to bisect the change that broke artifact builds I no longer get this error on fx-team tip (in the same cset where I used to get it).

Comment 2

2 years ago
Not getting this on fx-team anymore either. Should we close the bug?
I guess so. I wonder if it was a case where the downloaded artifacts weren't recent enough for the local build to pass.
Last Resolved: 2 years ago
Resolution: --- → WORKSFORME
For reference, the patch that recently landed for bug 1114647 didn't change the set of installed files, so in theory it shouldn't have caused this.  (An earlier attempt in April — bug 1114647 comment #59 through 75 — did rename plugin-container but was backed out.)
I hit this again today.
Resolution: WORKSFORME → ---

Comment 6

2 years ago
Yeah me too on the latest central (f8e3b81a79f4)
It is interesting that in the objdir there is this empty directory: dist/bin/

Comment 8

a year ago
Hit this again today on central and inbound.
My colleague aswan and I are both seeing this today with artifact builds on OS X. They fail with this same error message.

Comment 10

11 months ago
The timing sounds like it may be related to bug 1295375.

However, `hg bisect` says it is from This is almost certainly because that was a push head for the mozilla-central push/merge where universal os x builds were dropped.
Depends on: 1295375

Comment 11

11 months ago
What branch+revision is the artifact build grabbing? I took a quick look at a random package before and after the universal build change and both have the same paths for plugin-container, so I'm not sure why this would start failing now.

Comment 12

11 months ago
I took a look and here's what is happening.

According to, it is looking for a 'public/build/firefox-(.*).mac.dmg' on taskcluster. However, taskcluster is now listing the opt builds as 'mac64' not 'mac':

Looking at, we can also see that the nightly builds have changed from 'mac' to 'mac64' (there's both sets in there currently).

I'm guessing that change is wrong and is going to upset everyone.

Due to the switch away from universal binaries, we're now hitting the else part of the ifdef here:

I think the simple solution is just to update that ifdef. I'll get a patch up in a few.
Comment hidden (mozreview-request)

Comment 14

11 months ago
My local builds & the try builds appear to be ok with this change.

Comment 15

11 months ago
Comment on attachment 8818223 [details]
Bug 1278812 - Change default mac filename to be 'mac' rather than 'mac64' now that bug 1295375 has moved us away from universal builds.

Good catch.

This does mean we'll be unable to find artifacts across TC index renames. But this should be rare, so hopefully we can ignore this edge case.

Also, the `` should have ideally been split to its own commits, as it has more to do with cleaning up recently-unused code. But meh. Happy to see all references to the old platform name nuked.
Attachment #8818223 - Flags: review?(gps) → review+

Comment 16

11 months ago
Pushed by
Change default mac filename to be 'mac' rather than 'mac64' now that bug 1295375 has moved us away from universal builds. r=gps


11 months ago
Assignee: nobody → standard8

Comment 17

11 months ago
Last Resolved: 2 years ago11 months ago
status-firefox53: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla53
I can confirm that this fixes the issue for me. Thanks for the fix.
You need to log in before you can comment on or make changes to this bug.