Closed Bug 691670 Opened 8 years ago Closed 7 years ago

Build error: File exists: '../../dist/bin/chrome/browser/content/browser'


(Firefox Build System :: General, defect)

Not set


(Not tracked)



(Reporter: justin.lebar+bug, Unassigned)



(Keywords: intermittent-failure)

My latest Linux32 build [1] errored out with

  OSError: [Errno 17] File exists: '../../dist/bin/chrome/browser/content/browser'

Blocks: 438871
Whiteboard: [orange]
I didn't quite understand bug 678021, where the problem was that both browser/base/ and browser/devtools/ were in PARALLEL_DIRS and were both touching browser.jar, since that's also true of multiple things in browser/components/ and browser/themes/. Apparently the answer to my confusion was "we just hadn't gotten around to caring about the way we break there, too."
We had lots of nice locking code in for racing to create jars, and then we switched to omnijar and stopped making jars, and it conveniently doesn't have any locking code (or sufficient locking code) for racing to create directories of flat files.
Mass marking whiteboard:[orange] bugs WFM (to clean up TBPL bug suggestions) that:
* Haven't changed in > 6months
* Whose whiteboard contains none of the strings: {disabled,marked,random,fuzzy,todo,fails,failing,annotated,leave open,time-bomb}
* Passed a (quick) manual inspection of bug summary/whiteboard to ensure they weren't a false positive.

I've also gone through and searched for cases where the whiteboard wasn't labelled correctly after test disabling, by using attachment description & basic comment searches. However if the test for which this bug was about has in fact been disabled/annotated/..., please accept my apologies & reopen/mark the whiteboard appropriately so this doesn't get re-closed in the future (and please ping me via IRC or email so I can try to tweak the saved searches to avoid more edge cases).

Sorry for the spam! Filter on: #FFA500
Closed: 7 years ago
Resolution: --- → WORKSFORME
Whiteboard: [orange]
Product: Core → Firefox Build System
You need to log in before you can comment on or make changes to this bug.