Closed Bug 925494 Opened 9 years ago Closed 9 years ago

clock app no longer showing up in datazilla launch tests


(Firefox OS Graveyard :: General, defect)

Not set


(Not tracked)



(Reporter: bkelly, Unassigned)



(Keywords: perf, Whiteboard: [c=automation p= s=2013.10.25 u=])

It looks like the clock app stopped showing up in datazilla cold_launch test results around 9/30.  It looks like the app is there in the jenkins config, but perhaps I'm looking at the wrong job.
Dave, any ideas why clock is no longer showing up?
Flags: needinfo?(dave.hunt)
Yes, this is blocked by bug 921194. I get mixed results replicating this locally, but when it fails it almost always appears to affect the restart immediately before the first clock launch in the b2gperf testruns.
Depends on: 921194
Flags: needinfo?(dave.hunt)
I tried moving the Browser app launch from immediately before the Clock app launch to the end. This allowed the Clock app launch to succeed but caused the "FM Radio" app launch to fail, which was now immediately after Clock in the list. I have also been unable to replicate this when removing the 60 second sleep after each restart, which implies to me this is related to uptime or time since the device was flashed. I'm continuing to investigate locally.
Keywords: perf
Whiteboard: [c=automation p= s= u=]
This appears to be fixed in datazilla now.
Closed: 9 years ago
Resolution: --- → FIXED
Whiteboard: [c=automation p= s= u=] → [c=automation p= s=2013.10.25 u=]
You need to log in before you can comment on or make changes to this bug.