Closed Bug 840252 Opened 12 years ago Closed 12 years ago

Contacts app dying in MW2

Categories

(Firefox OS Graveyard :: Gaia, defect)

Product:
Firefox OS Graveyard
Component:
Gaia
Platform:
x86_64
Linux
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(blocking-b2g:-, b2g18+)

Status:
RESOLVED WORKSFORME
Project Flags:
blocking-b2g -
Tracking Flags:
Tracking Status
b2g18 + ---

People

(Reporter: cjones, Assigned: vingtetun)

References

Details

(Keywords: regression)

STR (1) Follow steps in https://wiki.mozilla.org/B2G/Memory_acceptance_criteria#MW2:_Active_call_stays_active The image for the new contact after step 22 isn't delivered because the contacts app is killed. Did something regress in the way we treat apps during activities?
Needs to block.
blocking-b2g: --- → tef?
Blocking for now based on current understanding of acceptance criteria. We will review this tomorrow in a partner triage session to confirm if it will remain blocking.
Assignee: nobody → 21
blocking-b2g: tef? → tef+
There are no clear steps forward here, and this isn't associated with comms/alarm. Tracking instead of blocking.
blocking-b2g: tef+ → -
tracking-b2g18: --- → +
(In reply to Alex Keybl [:akeybl] from comment #3) > There are no clear steps forward here I don't follow? Find and fix the regression? I haven't seen this in the last few runs though so I guess timing is different again.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
(In reply to Chris Jones [:cjones] [:warhammer] from comment #4) > I don't follow? Find and fix the regression? We're days away from being done, we haven't seen this in user testing, LMK of contacts isn't as critical as comms/alarm, and a final solution isn't yet evident. The risk/reward scale is tipping much farther in the risk direction. If you think this is a very recent regression (and thus a lower risk fix may be possible), we can add the qawanted/regressionwindow-wanted keywords to get QA's help.
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
Alex, did you mean to reopen the bug?
(In reply to Justin Lebar [:jlebar] from comment #6) > Alex, did you mean to reopen the bug? nope, sorry
Status: REOPENED → RESOLVED
Closed: 12 years ago → 12 years ago
Resolution: --- → WORKSFORME
(In reply to Alex Keybl [:akeybl] from comment #5) > (In reply to Chris Jones [:cjones] [:warhammer] from comment #4) > > I don't follow? Find and fix the regression? > > We're days away from being done, we haven't seen this in user testing, LMK > of contacts isn't as critical as comms/alarm, and a final solution isn't yet > evident. The risk/reward scale is tipping much farther in the risk direction. What does any of this have to do with having a path forward? I get the impression we're talking past each other, which is unfortunate. Not the best medium for communication, here. At any rate, this is no longer reproducing so let's hope we picked up a mystery fix.
You need to log in before you can comment on or make changes to this bug.