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

See Changes: [Kaleb S. KEITHLEY] Portability fix: rfc.sh -- [...truncated 1959 lines...] ++ sed -ne 's/.*\([01]\)<\/status>/\1/p' ++ exit 0 + a=0 + '[' 0 -ne 0 ']' + [[ 0 =~ 1 ]] + sleep 1

[Gluster-Maintainers] Jenkins build is back to normal : regression-test-burn-in #246

See ___ maintainers mailing list maintainers@gluster.org http://www.gluster.org/mailman/listinfo/maintainers

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

k-read.t .. ok 5669 ms [08:33:05] All tests successful. Files=1, Tests=20, 5 wallclock secs ( 0.02 usr 0.00 sys + 0.60 cusr 0.30 csys = 0.92 CPU) Result: PASS + RET=0 ++ ls -l /core.21357 ++ wc -l + cur_count=1 + '[' 1 '!=' 0 ']' + mkdir -p /build/install/cores + mv /core.21357 /build/install/core

[Gluster-Maintainers] IMPORTANT: New jenkins triggering method

We have now changed the gerrit-jenkins workflow as follows: 1. Developer works on a new feature/bug fix and tests it locally(run run-tests.sh completely). 2. Developer sends the patch to gerrit using rfc.sh. +++Note that no regression runs have started automatically for this patch at this

Re: [Gluster-Maintainers] IMPORTANT: New jenkins triggering method

On Tue, Jan 12, 2016 at 07:21:37PM +0530, Raghavendra Talur wrote: > We have now changed the gerrit-jenkins workflow as follows: > > 1. Developer works on a new feature/bug fix and tests it locally(run > run-tests.sh completely). > 2. Developer sends the patch to gerrit using rfc.sh. > > +++Note

Re: [Gluster-Maintainers] [Gluster-devel] IMPORTANT: New jenkins triggering method

-Atin Sent from one plus one On Jan 12, 2016 7:41 PM, "Niels de Vos" wrote: > > On Tue, Jan 12, 2016 at 07:21:37PM +0530, Raghavendra Talur wrote: > > We have now changed the gerrit-jenkins workflow as follows: > > > > 1. Developer works on a new feature/bug fix and tests it