[Gluster-Maintainers] Build failed in Jenkins: regression-test-burn-in #29

[Vijay Bellur]

On 12/06/2015 09:15 PM, Pranith Kumar Karampuri wrote:
> Failure happened because of the following dependencies:
> + /opt/qa/build.sh
> error: Failed dependencies:
>      libgfapi.so.0()(64bit) is needed by (installed)
> qemu-img-2:0.12.1.2-2.479.el6_7.2.x86_64
>      libgfapi.so.0()(64bit) is needed by (installed)
> qemu-kvm-2:0.12.1.2-2.479.el6_7.2.x86_64
>      glusterfs-api is needed by (installed)
> qemu-kvm-2:0.12.1.2-2.479.el6_7.2.x86_64
>      libgfrpc.so.0()(64bit) is needed by (installed)
> qemu-img-2:0.12.1.2-2.479.el6_7.2.x86_64
>      libgfrpc.so.0()(64bit) is needed by (installed)
> qemu-kvm-2:0.12.1.2-2.479.el6_7.2.x86_64
>      libgfxdr.so.0()(64bit) is needed by (installed)
> qemu-img-2:0.12.1.2-2.479.el6_7.2.x86_64
>      libgfxdr.so.0()(64bit) is needed by (installed)
> qemu-kvm-2:0.12.1.2-2.479.el6_7.2.x86_64
>

I modified an existing jenkins job over the weekend to run regression 
tests on our baseline, so please bear with me till it matures a bit.

There is a two fold intent in having this job:

1. Help us quickly identify and resolve spurious regression failures. 
All failures in the baseline jenkins job will be notified on this 
mailing list . I expect all of us to pay more attention to failures in 
our respective components when it happens in the baseline regression. 
The baseline job is setup to run once every 4 hours or so for now. Once 
our regression tests stabilize, the frequency can be altered to once per 
day or so.

2. Help us isolate patch induced regression failures in jenkins. If a 
failure does not happen at all in baseline runs but in regular 
regression runs, it will most likely be due to the patch being introduced.

I am interested in solving the problem associated with spurious 
regression runs for good in quick order. Your assistance in reaching 
there will be highly appreciated!

Thanks,
Vijay