All test cases failed in thermal_05 on Samsung Arndale Linux Linaro ubuntu.

[Botao]

On Samsung Arndale board wirh Linux Linaro ubuntu image:

http://snapshots.linaro.org/ubuntu/pre-built/arndale/630/arndale-saucy_server_20140417-630.img.gz

All test cases failed in thermal_05:

https://validation.linaro.org/dashboard/streams/private/team/linaro/pre-built-arndale/bundles/112bfeb2d49783da592accc59dde9bc923945cbe/5ec345a8-b18e-4dbb-9f3e-dbd74073388c/?search=fail&length=25

https://validation.linaro.org/dashboard/attachment/764543/view

### thermal_05:
### test/verify the cpufreq cooling device are clipping the frequencies
### https://wiki.linaro.org/WorkingGroups/PowerManagement/Resources/TestSuite/PmQaSpecification#thermal_05
###
thermal-cpufreq-0
thermal_05.0: checking cdev=cooling_device0 state=1... Err
thermal_05.1: checking cdev=cooling_device0 state=2... Err
thermal_05.2: checking cdev=cooling_device0 state=3... Err
thermal_05.3: checking cdev=cooling_device0 state=4... Err
thermal_05.4: checking cdev=cooling_device0 state=5... Err
thermal_05.5: checking cdev=cooling_device0 state=6... Err
thermal_05.6: checking cdev=cooling_device0 state=7... Err
thermal_05.7: checking cdev=cooling_device0 state=8... Err
thermal_05.8: checking cdev=cooling_device0 state=9... Err
thermal_05.9: checking cdev=cooling_device0 state=10... Err
thermal_05.10: checking cdev=cooling_device0 state=11... Err
thermal_05.11: checking cdev=cooling_device0 state=12... Err
thermal_05.12: checking cdev=cooling_device0 state=13... Err
thermal_05.13: checking cdev=cooling_device0 state=14... Err
thermal_05.14: checking cdev=cooling_device0 state=15... Err
-------- total = 15
-------- pass = 0
-------- fail = 15

Also, thermal_04.1 failed as well:

thermal_04.1: checking cooling_device0:state=2 effective cool=-1000 ... Err

By comparison, on build #627, all thermal test suites were ignored / skipped:

https://validation.linaro.org/dashboard/attachment/754046/view

If those features are not supported there, we'd better to remove them from the list.

[Amit Kucheria (amitk)]

PM-QA is supposed to show missing or buggy functionality in member software stack. So the bug should always be assigned to the member landing teams first.

If they determine it to be a bug in PM-QA itself, only then assign it to PMWG.