Johan Lorenzo [:jlorenzo] Reporter
	Description • 8 years ago

Seen at Bitbar[1] and in the lab[2]. I'm investigating. 

[1] http://jenkins1.qa.scl3.mozilla.com/view/Bitbar/job/flame-kk-512.b2g-inbound.tinderbox.ui.brick.bitbar/1871/console
[2] http://jenkins1.qa.scl3.mozilla.com/view/Brick/job/flame-kk-512.b2g-inbound.tinderbox.ui.brick/1817/console

	Johan Lorenzo [:jlorenzo] Reporter
	Comment 1 • 8 years ago

Based on the mozilla-inbound jobs[1], the regression window is: http://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=fcc73febb20cb72bb6716b48757b18c3f9044297&tochange=10c8b5b877b9e7bf11c6a472338496a7aa0d3a10

[1] Last working: http://jenkins1.qa.scl3.mozilla.com/view/Brick/job/flame-kk-512.mozilla-inbound.tinderbox.ui.brick/4121/console
First failing: http://jenkins1.qa.scl3.mozilla.com/view/Brick/job/flame-kk-512.mozilla-inbound.tinderbox.ui.brick/4123/console
Build #4122 failed for another reason.

	Johan Lorenzo [:jlorenzo] Reporter
	Comment 2 • 8 years ago

The Jenkins jobs didn't pick every inbound builds. I finished the regression window manually:
> 20160105125106 -> Last Working 
> 20160105130335 -> First broken https://tools.taskcluster.net/index/artifacts/#gecko.v2.mozilla-inbound.pushdate.2016.01.05.20160105130335.b2g/gecko.v2.mozilla-inbound.pushdate.2016.01.05.20160105130335.b2g.flame-kk-eng-opt
> 20160105141853 -> Broken
> 20160105142045
> 20160105144839 -> Broken
> 20160105153026
> 20160105154033 -> Broken
> 20160105160832
> 20160105161236
> 20160105164022
> 20160105165104
> 20160105165219
> 20160105165404 -> Broken
> 20160105171213
> 20160105171639
> 20160105172201
> 20160105172501
> 20160105181655
> 20160105191255
> 20160105191358
> 20160105200202
> 20160105200425
> 20160105200446
> 20160105200536
> 20160105202451
> 20160105202538 -> Broken

Push log: http://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=fcc73febb20cb72bb6716b48757b18c3f9044297&tochange=9f75805352143a6ea91abdfc163acff1adbe5f0a 

The push logs shows it's cause by bug 1221056. 

While performing the regression, I realized that the marionette connection being lost is just a symptom among others. Manually, you can see the phone is in an unusable state: The FTU pops, loads the locales, then turns black and goes back to the splash screen.

	Johan Lorenzo [:jlorenzo] Reporter
	Comment 4 • 8 years ago

Resolved by backout of bug 1221056.

	Martin Shuman [:Marty]
	Comment 5 • 8 years ago

This issue is verified fixed on the latest Flame Nightly build.
The device is able to properly boot to the FTU and progress to the homescreen.

Environmental Variables:
Device: Flame 2.6 [512MB]
BuildID: 20160107030227
Gaia: 676237f80cf72182500356fabc49365d3471c0e6
Gecko: e0bcd16e1d4b99ba3e542149d0d41e0f60c54b5c
Gonk: 205ac4204bbbb2098a8046444acba551ba5dc75a
Version: 46.0a1 (2.6) 
Firmware Version: v18D
User Agent: Mozilla/5.0 (Mobile; rv:46.0) Gecko/46.0 Firefox/46.0