memory_compare script was changed to a 25% variance allowed
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Checkbox Provider - Base |
Fix Released
|
Low
|
Daniel Manrique |
Bug Description
At some point in recent history, the memory_compare script was changed to pass on anything with a 25% variance or less in RAM. This was 10% historically and satisfied both client and server systems.
With a 10% variance, clients (mostly laptops) with shared RAM that use more than 10% are flagged but everything else is passed (assuming they vary by 10% or less).
With the 25% we run the very real risk of missing cases where RAM variance between the kernel is significantly different from what's physically there without being flagged by a test failure to investigate further.
A recent example, we had a server that had 512MB difference between what was physically installed and what the kernel addressed. the 10% test flagged this and on investigation, the system was passed once we did some digging and discovered that the server used an AMD APU that also had a built in GPU that was using 512MB of RAM, thus the discrepancy.
However, had this test run using the new 25% limit, it very likely would not have been noticed, and if it was not a GPU shared ram issue, we would have overlooked a potentially 25% gap in RAM that had no explanation other than hardware or kernel bug.
So a question that came to mind is this (thinking of it from a client cert perspective):
If a laptop is certified with 8GB of ram, and is sharing 1GB, but the variance is the full 25%, there would be 1 full GB of RAM unaccounted for that may go unnoticed because of the wider limit on this test.
I haven't found exactly when this change occurred, but a recent server certificate, tested at the beginning of June with this version from the dev ppa:
plainbox-
still showed the 10% variance
Related branches
- Jeff Lane : Approve
-
Diff: 125 lines (+48/-12)1 file modifiedproviders/plainbox-provider-checkbox/bin/memory_compare (+48/-12)
Changed in plainbox-provider-checkbox: | |
milestone: | none → 0.10 |
Changed in plainbox-provider-checkbox: | |
status: | In Progress → Fix Committed |
Changed in plainbox-provider-checkbox: | |
status: | Fix Committed → Fix Released |
I first noticed this today while testing this version from the "testing" ppa
plainbox- provider- checkbox 0.9~c1~ ppa~ubuntu14. 04.1