[Gluster-devel] Regression failure due to bad test case

[Saravanakumar Arumugam]

Hi,
Thanks Atin! You are correct.
<<<<<<<<<<
+ '[' 1 '!=' 0 ']'
+ set +x
Going to copy log tarball for processing on http://elk.cloud.gluster.org/
sort: write failed: standard output: Broken pipe
sort: write error
Build step 'Execute shell' marked build as failure
Finished: FAILURE
<<<<<<<<<<

I remember facing similar issue earlier.
Any idea how to overcome these types of failures apart from retriggering 
regression :) ?

Thanks,
Saravana


On 10/27/2015 02:13 PM, Atin Mukherjee wrote:
>
> On 10/27/2015 12:33 PM, Saravanakumar Arumugam wrote:
>> Hi,
>> I am facing regression failure http://review.gluster.org/#/c/12239
>>
>> https://build.gluster.org/job/rackspace-regression-2GB-triggered/15166/consoleFull
>>
>>
>> But both the test cases are marked bad??
>>
>> ./tests/bugs/glusterd/bug-948686.t
>>   ./tests/bugs/glusterd/bug-1238706-daemons-stop-on-peer-cleanup.t
>>
>> It should be success as both the test cases are marked as bad ??
> I don't think the failure was due to a bad test not passing regression.
> All the tests passed apart from bad test(s). Copying the log tarball to
> a location actually failed here. See at the bottom of the page.
>
> ~Atin
>> Please refer the log for details.
>>
>> Thanks,
>> Saravana
>>
>>
>>
>>
>> _______________________________________________
>> Gluster-devel mailing list
>> Gluster-devel at gluster.org
>> http://www.gluster.org/mailman/listinfo/gluster-devel