Closed Bug 936316 Opened 11 years ago Closed 10 years ago

[Endurance Test] Turn FM Radio on and off

Categories

(Remote Protocol :: Marionette, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: wachen, Assigned: rwood)

References

Details

In MTBF draft run, I found that within few thousand(4000~5000) of turning on and off fm, the fm will never be able to recover. I need rwood's helping on creating a single test and just run it few thousand times. Thanks.
Rwood told me that he could take care of this later!
Assignee: nobody → rwood
Not sure if this a memory leak or some other fault.
Walter, can you attach the script you used to turn on and off fm?
Flags: needinfo?(wachen)
from gaiatest import GaiaMtbfTestCase from gaiatest.apps.fmradio.app import FmRadio class TestFMRadioTurnOnOff(GaiaMtbfTestCase): def setUp(self): GaiaMtbfTestCase.setUp(self) self.fm_radio = FmRadio(self.marionette) self.app_id = self.launch_by_touch("FM Radio") def test_turn_radio_on_off(self): # check the headphone is plugged-in or not self.assertTrue(self.data_layer.is_antenna_available, 'Antenna (headphones) not plugged in') # turn the radio off self.fm_radio.tap_power_button() # check the radio is off self.fm_radio.wait_for_radio_off() self.assertFalse(self.data_layer.is_fm_radio_enabled) # turn the radio on self.fm_radio.tap_power_button() self.wait_for_condition(lambda m: self.data_layer.is_fm_radio_enabled) # check the radio is on self.assertTrue(self.fm_radio.is_power_button_on) self.assertTrue(self.data_layer.is_fm_radio_enabled) def tearDown(self): if self.fm_radio.is_power_button_on: self.fm_radio.tap_power_button() GaiaMtbfTestCase.tearDown(self)
Flags: needinfo?(wachen)
any help would be appreciated. thanks.
I'll write an endurance test and see if I can reproduce the issue.
Update: I wrote an endurance test for this, and ran it on hamachi with the latest 1.2. It passed fine with 5000 iterations. I used the same code that :ypwalter used above, except in an endurance test, and I added a 2 second pause between each iteration. Walter, I would suggest adding a couple second sleep to your MTBF test, and try it again. Perhaps the device got into a bad state as it didn't have any down time for GC. Although with more than one MTBF test, this specific test won't be repeated thousands of times consecutively anyway correct (it will be mixed in with other tests).
Thanks so much. I will try to figure if that's the problem in next test run. I will also try to add some time gap in between
Blocks: MTBF-meta
Blocks: MTBF-B2G
No longer blocks: MTBF-meta
I should try to run FMRadio Endurance test by MTBF one day.
Flags: needinfo?(wachen)
This one is okay now. I guess there was some fixes for this or something
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WORKSFORME
Flags: needinfo?(wachen)
Product: Testing → Remote Protocol
You need to log in before you can comment on or make changes to this bug.