The tests for gnome-power-manager-2.20.0 fail for me due to not having a battery device on my desktop machine: > check #66 GpmCellUnit: make sure hal type set correct......OK [type correct] > check #67 GpmCellUnit: make sure full battery isn't charged......OK [not charged] > check #68 GpmCellUnit: make sure string type is okay......OK [string type okay] > check #69 GpmCellUnit: make sure single localised type is okay......OK [localised type okay] > check #70 GpmCellUnit: make sure plural localised type is okay......OK [localised type okay] > check #71 GpmCellUnit: make sure charging battery isn't charged......OK [not charged] > check #72 GpmCellUnit: make sure full battery is charged......OK [charged] > check #73 GpmCellUnit: make sure broken battery isn't charged......OK [not charged] > check #74 GpmCellUnit: get missing icon......OK [icon correct] > check #75 GpmCellUnit: get middle icon......OK [icon correct] > check #76 GpmCellUnit: get charged icon......OK [icon correct] > check #77 GpmCellUnit: setting measure......OK [measure correct] FAILED [did not find battery device] FAIL: gnome-power-self-test
fails even with a battery present. Would be great if you could point upstream to this bug.
Filed as http://bugzilla.gnome.org/show_bug.cgi?id=497908 Giles, you might also want to append some details on your specific failure there.
I'm getting the results described at the end of the upstream bug: > check #81 GpmCell: can we assign device......OK [set type okay] > check #82 GpmCell: make sure we got a single recall notice...FAILED [did not get recall (install fdi?)] FAIL: gnome-power-self-test What extra information would help diagnose this? I'm running this on a laptop with a battery.
2.22.1 got tests restricted. I've added some comments on upstream bug, we'll see how it goes.
g-p-m 2.26 has test-suite fixed and hopefully following revisions will stick to this state. Closing fixed.