Closed
Bug 1187743
Opened 10 years ago
Closed 10 years ago
shallowflash of nightly builds fails on Gaia push
Categories
(Firefox OS Graveyard :: General, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: davross, Unassigned)
References
Details
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:39.0) Gecko/20100101 Firefox/39.0
Build ID: 20150630154324
Steps to reproduce:
$ ./shallow_flash.sh --gaia=gaia.zip --gecko=b2g-42.0a1.en-US.android-arm.tar.gz
over the July 12 updated nightly base image
Actual results:
Gecko succeeds, Gaia fails, Flame goes black.
Performed another shallowflash for Gaia on its own and it succeeded
Expected results:
Smooth as silk update
| Reporter | ||
Comment 1•10 years ago
|
||
Using the 20150729 images, Gaia again fails whilst it hangs in the shallowflash procedure. I've had to CTRL-C to cancel to the process and remove the battery.
Running the shallowflash with the Flame screen black I do
./shallow_flash.sh --gecko=b2g-42.0a1.en-US.android-arm.tar.gz
which succeeds and reboots
then
./shallow_flash.sh --gaia=gaia.zip
and it works.
Seems it's a recurring issue I have been experiencing see bug 1185290
| Reporter | ||
Comment 2•10 years ago
|
||
This is now happening when running a shallow flash of b2g on its own. Occurred at least the last 2 nightlies. Have had to remove battery to start handset again. It does work eventually, but leaves me with my heart in my mouth.
20150815.b2g-43.0a1.en-US.android-arm.tar.gz
| Reporter | ||
Comment 3•10 years ago
|
||
and has now brought back the https certificate problems seen in bug 1185290
trying a handset reset
restores to fully operational. I had to reset handset a few times last week due to another issue. This particular bug has remained.
| Reporter | ||
Comment 4•10 years ago
|
||
Shallow Flash from 20150821 has gone through without error.
Will wait on one more update as confirmation before closing.
| Reporter | ||
Updated•10 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 10 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•