Comment 46 for bug 1640547

Revision history for this message
Mike Rushton (leftyfb) wrote :

Looks like this one is finally resolved. These are the results from my recent testing:

Result,Timestamp,Test Name,Duration,kernel,Package version,CPU's,Memory,Package,Note
PASS,2017-02-21-19-39-20,disk_stress_ng,01:48:24,4.4.0-63-generic-84-Ubuntu,0.07.16-1ppa1,128,31G,Stock stress-ng, stock kernel, colins changes to disk_stress_ng script
PASS,2017-02-21-21-45-09,disk_stress_ng,01:43:45,4.4.0-63-generic-84-Ubuntu,0.07.16-1ppa1,128,31G,Stock stress-ng, stock kernel, colins changes to disk_stress_ng script
PASS,2017-02-22-15-22-25,disk_stress_ng,01:44:35,4.4.0-64-generic-85-Ubuntu,0.07.16-1ppa1,128,31G,Stock stress-ng, stock kernel, colins changes to disk_stress_ng script
PASS,2017-02-27-17-51-38,disk_stress_ng,01:51:26,4.4.0-64-generic-85-Ubuntu,0.07.21-1~ppa,128,31G,Fresh Deployment
PASS,2017-02-27-20-04-49,disk_stress_ng,01:51:38,4.4.0-64-generic-85-Ubuntu,0.07.21-1~ppa,128,31G,fresh deployment
PASS,2017-02-27-22-44-36,disk_stress_ng,01:54:38,4.4.0-64-generic-85-Ubuntu,0.07.21-1~ppa,128,31G,fresh deployment