Hi, Thanks for the amazing work! I've been a happy artifact build user for the past few days, and I can confirm this is a life changer.
I wanted to report an issue I just had though, and wasn't sure where I should file a bug. I just pulled from fx-team and run ./mach build (with my .mozconfig being configured to build in artifact mode). This worked fine and I went on to try and run a devtools mochitest test (which worked fine yesterday). The test didn't manage to start properly (the browser window did appear, but remained blank) and the following error was present multiple times in the logs: JavaScript error: file:///c:/Users/Patrick/dev/fx-team/objdir-frontend/dist/bin/components/SanityTest.js, line 160: NS_NOINTERFACE: ************************* A coding exception was thrown in a Promise resolution callback. See https://developer.mozilla.org/Mozilla/JavaScript_code_modules/Promise.jsm/Promise Full message: ReferenceError: OfflineCacheInstaller is not defined Full stack: this.DOMApplicationRegistry.updateOfflineCacheForApp/<@resource://gre/modules/Webapps.jsm:511:9 Handler.prototype.process@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:933:23 this.PromiseWalker.walkerLoop@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:812:7 Promise*this.PromiseWalker.scheduleWalkerLoop@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:743:11 this.PromiseWalker.schedulePromise@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:775:7 this.PromiseWalker.completePromise@resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js:710:7 this.AppsUtils.loadJSONAsync/<@resource://gre/modules/AppsUtils.jsm:746:11 NetUtil_asyncFetch/<.onStopRequest@resource://gre/modules/NetUtil.jsm:128:17 ************************* Is there something I can do to work around this? Should I file a bug, and if so, which component should I report it in? On Wed, Jan 20, 2016 at 12:09 AM, Christopher Manchester < [email protected]> wrote: > Support for test plugins landed on inbound earlier this afternoon. This > required modifying rules for installation paths, so some cached archives > will be invalidated by this change. > > Please `rm ~/.mozbuild/package-frontend/*.processed.jar` after pulling to > avoid build bustage as a result of this change. An automatic solution for > re-generating caches in cases like these is tracked in > https://bugzilla.mozilla.org/show_bug.cgi?id=1240922 > > Chris > > On Mon, Jan 18, 2016 at 3:19 PM, Nicholas Alexander < > [email protected]> wrote: > >> Hi folks, >> >> On Thu, Dec 31, 2015 at 5:08 PM, Nicholas Alexander < >> [email protected]> wrote: >> >>> Hi folks, >>> >>> I just landed Bug 1207890 [1] and Bug 1216817 [2]. Together, they >>> implement Firefox "artifact builds" for Mac OS X Desktop. Artifact builds >>> download pre-built binary artifacts (like libxul) rather than compiling >>> them locally, trading download bandwidth for developer machine time. If >>> you work on the Firefox Desktop front-end on Mac OS X -- meaning you're >>> modifying JavaScript, XHTML, and CSS, and you're building on Mac OS X -- >>> this new build mode is meant for you. Locally, I produce a working Mac OS >>> X Firefox in about a minute. >>> >>> I've written a quick start guide at >>> http://www.ncalexander.net/blog/2015/12/31/firefox-artifact-builds-for-mac/ >>> and will be updating documentation in the next few weeks. >>> >>> I thoroughly expect issues in the wild. Please file tickets depending >>> on Bug 1207890 [1] and CC me. Discussion is best on dev-builds. >>> >> >> Thanks to the fine work of Chris Manchester, we should now have artifact >> builds on Desktop that install the test harness executables (like xpcshell >> and certutil) needed to run xpcshell and mochitests locally [1]. In >> addition, thanks to Dave Townsend for filing a ticket to track installing >> the test plugins as well -- they should be in place now too [2]. >> >> Please test and file fallout and follow-ups against [1]. >> >> Yours, >> Nick >> >> [1] https://bugzilla.mozilla.org/show_bug.cgi?id=1238320 >> [2] https://bugzilla.mozilla.org/show_bug.cgi?id=1240239 >> >> _______________________________________________ >> firefox-dev mailing list >> [email protected] >> https://mail.mozilla.org/listinfo/firefox-dev >> >> > > _______________________________________________ > firefox-dev mailing list > [email protected] > https://mail.mozilla.org/listinfo/firefox-dev > >
_______________________________________________ dev-builds mailing list [email protected] https://lists.mozilla.org/listinfo/dev-builds
