[Gluster-infra] [Bug 1471879] Smoke test failing with insufficient disk space

2017-07-17 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1471879 Nigel Babu changed: What|Removed |Added Status|NEW |CLOSED

[Gluster-infra] [Bug 1471879] Smoke test failing with insufficient disk space

2017-07-17 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1471879 --- Comment #2 from Karthik U S --- (In reply to Nigel Babu from comment #1) > Can you also mention the machine where you're seeing this failure? Build was on builder0.rht.gluster.org You can see the console output here:

[Gluster-infra] [Bug 1471879] Smoke test failing with insufficient disk space

2017-07-17 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1471879 Nigel Babu changed: What|Removed |Added CC||nig...@redhat.com

[Gluster-infra] [Bug 1447518] Need centos machine to validate test cases specific to brick multiplexing

2017-07-17 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1447518 --- Comment #6 from Mohit Agrawal --- Hi Nigel, I am still using this machine for other bugzilla. Regards Mohit Agrawal -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this

[Gluster-infra] [Bug 1447518] Need centos machine to validate test cases specific to brick multiplexing

2017-07-17 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1447518 --- Comment #5 from Nigel Babu --- Hi Mohit, are you done with this machine? -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug

[Gluster-infra] [Bug 1471879] New: Smoke test failing with insufficient disk space

2017-07-17 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1471879 Bug ID: 1471879 Summary: Smoke test failing with insufficient disk space Product: GlusterFS Version: mainline Component: project-infrastructure Assignee: b...@gluster.org

[Gluster-infra] [Bug 1454423] github link in gerrit webpage needs a better parser

2017-07-17 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1454423 Nigel Babu changed: What|Removed |Added Status|VERIFIED|CLOSED

Re: [Gluster-infra] Jenkins and Gerrit issues today

2017-07-17 Thread Nigel Babu
We just started using the Jenkins pipeline and its associated plugins: https://build.gluster.org/job/nightly-master/ On Mon, Jul 17, 2017 at 6:08 PM, Michael Scherer wrote: > Le vendredi 14 juillet 2017 à 13:00 +0530, Nigel Babu a écrit : > > Hello, > > > > ## Highlights >

[Gluster-infra] [Bug 1471789] slave27 has been disabled because of " failed to write new configuration file .git/config.lock"

2017-07-17 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1471789 Nigel Babu changed: What|Removed |Added Status|NEW |CLOSED

Re: [Gluster-infra] Did we exhausted the disk space?

2017-07-17 Thread Nigel Babu
Please file a bug: https://bugzilla.redhat.com/enter_bug.cgi?product=GlusterFS=project-infrastructure On Mon, Jul 17, 2017 at 6:17 PM, Karthik Subrahmanya wrote: > Hi, > > One of my patch[1] just failed smoke test with error: > > Disk Requirements:At least 21MB more space

[Gluster-infra] Did we exhausted the disk space?

2017-07-17 Thread Karthik Subrahmanya
Hi, One of my patch[1] just failed smoke test with error: Disk Requirements:At least 21MB more space needed on the / filesystem. [1] https://review.gluster.org/#/c/17485/ Regards, Karthik ___ Gluster-infra mailing list Gluster-infra@gluster.org

[Gluster-infra] [Bug 1471789] New: slave27 has been disabled because of " failed to write new configuration file .git/config.lock"

2017-07-17 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1471789 Bug ID: 1471789 Summary: slave27 has been disabled because of "failed to write new configuration file .git/config.lock" Product: GlusterFS Version: 3.11 Component:

Re: [Gluster-infra] Jenkins and Gerrit issues today

2017-07-17 Thread Michael Scherer
Le vendredi 14 juillet 2017 à 13:00 +0530, Nigel Babu a écrit : > Hello, > > ## Highlights > * If you pushed a patch today or did "recheck centos", please do a recheck. > Those jobs were not triggered. > * Please actually verify that the jobs for your patches have started. You > can do that by