memory_compare script doesn't work properly on systems with multiple memory slots installed
Bug #1204013 reported by
Brendan Donegan
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Checkbox |
Fix Released
|
Medium
|
Unassigned |
Bug Description
After changing the memory_compare script to use lshw to find the installed memory size, we are now finding some systems return 0 for the installed memory. This seems to be because they have multiple 'banks' of memory installed and lshw reports this in a slightly different way, with a parent 'memory' node and child 'bank' nodes. The script should handle this eventuality.
Related branches
lp:~brendan-donegan/checkbox/bug1204013
- Daniel Manrique (community): Approve
-
Diff: 44 lines (+11/-3)2 files modifiedcheckbox-old/debian/changelog (+2/-0)
checkbox-old/scripts/memory_compare (+9/-3)
tags: | added: scripts |
Changed in checkbox: | |
status: | New → Fix Committed |
Changed in checkbox: | |
importance: | Undecided → Medium |
Changed in checkbox: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.