remove memory test from ubuntu friendly whitelist (default)
Bug #853799 reported by
Victor Tuson Palau
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Checkbox |
Fix Released
|
Critical
|
Jeff Lane | ||
Ubuntu Friendly |
Fix Released
|
Critical
|
Jeff Lane | ||
checkbox (Ubuntu) |
Fix Released
|
Critical
|
Unassigned |
Bug Description
multiple users a reporting issues with this test, it seems to doing some kind of memory stress testing that is not required for UF
Related branches
lp:~bladernr/checkbox/remove-memcheck-from-default-whitelist
- Brendan Donegan (community): Approve
-
Diff: 11 lines (+0/-1)1 file modifieddata/whitelists/default.whitelist (+0/-1)
lp:~roadmr/ubuntu/oneiric/checkbox/0.12.8
- Mathieu Trudel-Lapierre: Approve
- Ubuntu branches: Pending requested
-
Diff: 12410 lines (+2530/-1911)31 files modifiedcheckbox/job.py (+1/-1)
checkbox/lib/transport.py (+14/-4)
checkbox_gtk/gtk_interface.py (+5/-2)
data/whitelists/default.whitelist (+3/-14)
debian/changelog (+56/-0)
debian/po/de.po (+28/-16)
debian/po/it.po (+10/-9)
debian/po/pt_BR.po (+9/-7)
gtk/checkbox-gtk.desktop.in (+1/-1)
jobs/mediacard.txt.in (+6/-6)
jobs/miscellanea.txt.in (+2/-2)
jobs/suspend.txt.in (+3/-3)
plugins/apport_prompt.py (+2/-0)
plugins/intro_prompt.py (+14/-7)
plugins/launchpad_exchange.py (+6/-2)
plugins/suites_prompt.py (+4/-0)
po/de.po (+457/-301)
po/gl.po (+274/-301)
po/hu.po (+16/-16)
po/it.po (+36/-37)
po/pt_BR.po (+431/-339)
po/ru.po (+491/-321)
po/sl.po (+461/-227)
po/zh_HK.po (+126/-213)
scripts/connect_wireless (+4/-3)
scripts/cpu_scaling_test (+50/-9)
scripts/internet_test (+2/-2)
scripts/network_check (+3/-5)
scripts/reconnect (+0/-5)
scripts/resolution_test (+14/-57)
scripts/usb_test (+1/-1)
Changed in checkbox: | |
importance: | Undecided → Critical |
status: | New → Confirmed |
Changed in checkbox: | |
assignee: | Canonical Hardware Certification (canonical-hw-cert) → Jeff Lane (bladernr) |
Changed in checkbox: | |
status: | Confirmed → Fix Committed |
Changed in checkbox (Ubuntu): | |
status: | New → Triaged |
importance: | Undecided → Critical |
Changed in ubuntu-friendly: | |
status: | New → Fix Committed |
assignee: | nobody → Jeff Lane (bladernr) |
importance: | Undecided → Critical |
Changed in checkbox: | |
status: | Fix Committed → Fix Released |
Changed in ubuntu-friendly: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
So what this test does is it allocates more than free memory (thus forcing swap to be used) for 60 seconds then just free memory for 15 mins. I can't think of a good reason why the second load needs to be run at all unless for performance/load testing purposes. I suggest we change the memory/check test to just do the first part and then create a seperate memory/stress test that can run for as long as we want.