Closed
Bug 922467
Opened 13 years ago
Closed 13 years ago
Hamachi fails to start, due to "SettingsService failed to open DB!" after flashing Hamachi with the latest mozilla-central engineering build
Categories
(Core :: DOM: Device Interfaces, defect)
Core
DOM: Device Interfaces
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: stephend, Unassigned)
References
Details
(Keywords: regression)
Build info:
Gecko: 4d7401a1778508ff6942e6cf4dded618cefc63db
Gaia: e7c011371aa6af696033d4b867fb9152a6985efa
1) Here's our flash script: http://pastebin.mozilla.org/3174562
2) Here's our flashing output from the above, on a Hamachi device, using the engineering builds from mozilla-central: http://pastebin.mozilla.org/3174584
3) Here's the full logcat showing the Settings app/JSON problem: http://pastebin.com/HJDzciqd
On line 851 in the above pastebin 3), we see:
I/Gecko ( 141): SettingsService failed to open DB!
Caveat: I'm not convinced we're doing enough on-device cleanup with the script from 2) so help there is appreciated to, if it can help us either work around or "fix" this bug, but filing on the chance there's a real bug here.
Comment 1•13 years ago
|
||
Questions:
1. When is the last time you were able to get Hamachi to start up? Trying to get a regression range for debugging.
2. Is this device-specific or applies to all engineering builds?
Updated•13 years ago
|
Keywords: regression,
regressionwindow-wanted
| Reporter | ||
Comment 2•13 years ago
|
||
(In reply to Jason Smith [:jsmith] from comment #1)
> Questions:
>
> 1. When is the last time you were able to get Hamachi to start up? Trying to
> get a regression range for debugging.
According to our Jenkins, we at least passed a Wi-Fi unittest on a mozilla-central Hamachi build, on September 29th, around 7pm: http://qa-selenium.mv.mozilla.com:8080/view/B2G%20Hamachi/job/b2g.hamachi.mozilla-central.unittests.wifi/buildTimeTrend and http://qa-selenium.mv.mozilla.com:8080/view/B2G%20Hamachi/job/b2g.hamachi.mozilla-central.unittests.wifi/128/
However, when I go back and use that build to flash, I get the same problem, indicating that -- at least if not directly caused by it -- we do seem to have a problem deleting or reading in settings.json...(see below)
> 2. Is this device-specific or applies to all engineering builds?
...which, honestly makes me unable, right now, to get a good regression range, as I've even gone back and used the 27th's builds -- which I know work, from CI runs -- and they have the same issue.
One thing we're doing in this situation that might come into play, is mixing Aurora and mozilla-central runs, on the same Hamachi devices; something we've done and currently are doing, even, with the few remaining Inaris and Unagis we have left, and they don't seem to have this problem, but they have a different flash script, too.
Comment 3•13 years ago
|
||
>
> > 2. Is this device-specific or applies to all engineering builds?
>
> ...which, honestly makes me unable, right now, to get a good regression
> range, as I've even gone back and used the 27th's builds -- which I know
> work, from CI runs -- and they have the same issue.
>
> One thing we're doing in this situation that might come into play, is mixing
> Aurora and mozilla-central runs, on the same Hamachi devices; something
> we've done and currently are doing, even, with the few remaining Inaris and
> Unagis we have left, and they don't seem to have this problem, but they have
> a different flash script, too.
Usually we don't support this but I don't think it actually matter right now since we didn't change anything related to indexedDB versions.
| Reporter | ||
Comment 4•13 years ago
|
||
We're actually past this failure now -- hopefully for good (I'd like a little more bake time across the branches/jobs, before claiming victory; we've added:
adb shell stop b2g
adb root
adb shell rm -r /data/local/storage/persistent/*
To jobs, just before a device reboot/restart, with great success so far! Here's hoping...
Updated•13 years ago
|
Keywords: regressionwindow-wanted
| Reporter | ||
Comment 6•13 years ago
|
||
(In reply to Gregor Wagner [:gwagner] from comment #5)
> Can we close this now?
Yes, thanks for the re-ping. Closing as WFM.
Status: NEW → RESOLVED
Closed: 13 years ago
Flags: needinfo?(stephen.donner)
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•