Closed
Bug 660182
Opened 13 years ago
Closed 13 years ago
clientproxy is not attempting to reset error.flg after max hardReset is passed
Categories
(Release Engineering :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: bear, Assigned: bear)
Details
(Whiteboard: [android][tegra])
Attachments
(1 file)
1.51 KB,
patch
|
mozilla
:
review+
bear
:
checked-in+
|
Details | Diff | Splinter Review |
for each N soft resets the code tries a hard reset and after P hard resets it is supposed to reset them to zero if the heartbeat is active. Currently the soft reset is zero'd but not the hard reset so after it works it's way thru N soft and P hard, it never sends a reboot request (which is where the soft count is zero'd) so it just never tries again
Assignee | ||
Updated•13 years ago
|
Assignee: nobody → bear
Whiteboard: [android][tegra]
Assignee | ||
Comment 1•13 years ago
|
||
Attachment #535587 -
Flags: review?(aki)
Comment 2•13 years ago
|
||
Comment on attachment 535587 [details] [diff] [review] reset hard count when dialback event happens Nice catch.
Attachment #535587 -
Flags: review?(aki) → review+
Assignee | ||
Comment 3•13 years ago
|
||
Comment on attachment 535587 [details] [diff] [review] reset hard count when dialback event happens committed changeset 1455:790352c8011f
Attachment #535587 -
Flags: checked-in+
Assignee | ||
Updated•13 years ago
|
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•