On Thu, Oct 08, 2015 at 03:37:07PM +0530, Milind Changire wrote: > https://build.gluster.org/job/rackspace-regression-2GB-triggered/14782/consoleFull > > says > > Going to copy log tarball for processing on http://elk.cloud.gluster.org/ > scp: /srv/jenkins-logs/upload/jenkins-rackspace-regression-2GB-triggered-14782.tgz: > No space left on device > Build step 'Execute shell' marked build as failure > Finished: FAILURE Thanks for reporting, space free'd up. However, that is not the failure that caused the regression test to fail (this failure is silently ignored). The actual problem is this one: [09:39:49] ./tests/bugs/quota/bug-1260545.t .. not ok 12 not ok 13 Got "20.0MB" instead of "10.0MB" not ok 20 Got "20.0MB" instead of "10.0MB" Failed 3/23 subtests [09:39:49] Test Summary Report ------------------- ./tests/bugs/quota/bug-1260545.t (Wstat: 0 Tests: 23 Failed: 3) Failed tests: 12-13, 20 Files=1, Tests=23, 56 wallclock secs ( 0.02 usr 0.00 sys + 5.44 cusr 1.42 csys = 6.88 CPU) Result: FAIL ./tests/bugs/quota/bug-1260545.t: bad status 1 Running failed test ./tests/bugs/quota/bug-1260545.t in debug mode Just for debug data, does not change test result HTH, Niels
Attachment:
pgpHbMMokAP6m.pgp
Description: PGP signature
_______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-devel
