STR: 1. Get a unagi device 2. Flash the phone with: https://pvtbuilds.mozilla.org/pub/mozilla.org/b2g/nightly/mozilla-central-unagi-eng/latest/unagi.zip 3. Wait for the phone to start Expected: 3. the FTU screen should be visibile Actual: 3. The phone won't start it is stuck with the lights on and a black screen Build info: Gecko http://hg.mozilla.org/mozilla-central/rev/01576441bdc6 Gaia b582aaafdab26e78c2c4288c2b439d72d68dc9a4 BuildID 20130825040201 Version 26.0a1

Changing this to critical because we can't run any automation build on the build

the hone will start if we do: adb shell stop b2g start b2g

I'm seeing the following in the logs: E/GeckoConsole( 109): [JavaScript Error: "NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIProperties.get]" {file: "resource://gre/modules/FileUtils.jsm" line: 63}]

When is the last time we didn't hit this bug in gaia ui automation?

I think we unfortunately don't support master on Unagi now...

(In reply to Julien Wajsberg [:julienw] from comment #6) > I think we unfortunately don't support master on Unagi now... Where was this communicated? There are still builds for it (engineering and "regular") available: https://pvtbuilds.mozilla.org/pub/mozilla.org/b2g/nightly/mozilla-central-unagi-eng/ https://pvtbuilds.mozilla.org/pub/mozilla.org/b2g/nightly/mozilla-central-unagi/

I've been using B2G_DEBUG=1 builds of master on my unagi quite regularly. My current tree is probably a few days old, I'll try updating and see what happens.

It was a recent mail from Andreas on the dev.b2g mailing list, see https://groups.google.com/d/msg/mozilla.dev.b2g/DegSaEdFXa0/6zOiiYcun5cJ I don't have much more information...

(In reply to Julien Wajsberg [:julienw] from comment #9) > It was a recent mail from Andreas on the dev.b2g mailing list, see > https://groups.google.com/d/msg/mozilla.dev.b2g/DegSaEdFXa0/6zOiiYcun5cJ > > I don't have much more information... That doesn't make an effective justification for breaking the build entirely though. We're still migrating people away from unagi, so we shouldn't be causing the build to fail to start.

I can't reproduce this on an unagi production build on 8/26.

(In reply to Jason Smith [:jsmith] from comment #5) > When is the last time we didn't hit this bug in gaia ui automation? Our last good build (actual download) was from: [1] Build #39 (Aug 24, 2013 5:56:42 AM) - https://pvtbuilds.mozilla.org/pub/mozilla.org/b2g/nightly/mozilla-central-unagi-eng/2013/08/2013-08-24-04-02-25/ The one that failed to flash was: [2] Build #40 (Aug 25, 2013 5:56:42 AM) - https://pvtbuilds.mozilla.org/pub/mozilla.org/b2g/nightly/mozilla-central-unagi-eng/2013/08/2013-08-25-04-02-01/ Source.xml for those two: [1] https://pvtbuilds.mozilla.org/pub/mozilla.org/b2g/nightly/mozilla-central-unagi-eng/2013/08/2013-08-24-04-02-25/sources.xml [2] https://pvtbuilds.mozilla.org/pub/mozilla.org/b2g/nightly/mozilla-central-unagi-eng/2013/08/2013-08-25-04-02-01/sources.xml

I picked up https://pvtbuilds.mozilla.org/pub/mozilla.org/b2g/nightly/mozilla-central-unagi-eng/2013/08/2013-08-26-07-47-52/ and this is now flashing fine both locally and in our CI.