604527 - Automatic test for wakeups

Status: RESOLVED WONTFIX

(Firefox for Android Graveyard :: General, defect)

Description

[Alon Zakai (:azakai)]

Attachment: first stab

Attached is a first stab at an automatic test for wakeups. Instructions for running it are in the patch. Basically, it runs Fennec, waits, then runs powertop and parses the # of wakeups, then checks that is in the right range.

Test only works on Linux. Might also work on Android/Meego devices but not sure. However, testing on desktop Linux is very useful in itself (the # of wakeups is basically the same as on devices).

Need to think how to integrate such a test into our normal automatic test frameworks, etc.

Comment 1

[cmtalbert]

Forgive my ignorance, but what are you trying to measure and what is going to need to be installed on each device to make this work?  Is this something that needs to be measured during every test or only during a specific "wakeup measurement" - perhaps a Talos style test?

Comment 2

[Alon Zakai (:azakai)]

The test measures CPU wakeups - how many times the CPU goes from idle to doing something. Ideally we should have 0, when the browser is idle. But at least we should not regress on this.

The way to measure those is with 'powertop'. On ubuntu, |apt-get install powertop| gets it, it should be easily available elsewhere as well. (Note that powertop needs to be run with root privileges - 'sudo powertop' or such, which the test mentions.)

I think this should run with every commit, and not like Talos.

Comment 3

[Tony Chung [:tchung]]

We need this part of the automated tests ran against the nightlies.  in the meantime, we can probably add a litmus test and have the tester run the python script on their device each time a nightly build is installed.

Comment 4

[BMO Automation]

Closing all opened bug in a graveyard component