[Gluster-infra] [Bug 1350631] Some machines don't have /opt/qa updated
https://bugzilla.redhat.com/show_bug.cgi?id=1350631 --- Comment #5 from Nigel Babu --- [root@slave22 qa]# GIT_TRACE=1 git pull trace: exec: 'git-pull' trace: run_command: 'git-pull' trace: built-in: git 'rev-parse' '--git-dir' trace: built-in: git 'rev-parse' '--is-bare-repository' trace: built-in: git 'rev-parse' '--show-toplevel' trace: built-in: git 'ls-files' '-u' trace: built-in: git 'symbolic-ref' '-q' 'HEAD' trace: built-in: git 'config' '--bool' 'branch.master.rebase' trace: built-in: git 'config' '--bool' 'pull.rebase' trace: built-in: git 'rev-parse' '-q' '--verify' 'HEAD' trace: built-in: git 'fetch' '--update-head-ok' trace: run_command: 'git-remote-https' 'origin' 'https://github.com/gluster/glusterfs-patch-acceptance-tests.git' -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=czhXk1rLKF&a=cc_unsubscribe ___ Gluster-infra mailing list Gluster-infra@gluster.org http://www.gluster.org/mailman/listinfo/gluster-infra
[Gluster-infra] [Bug 1350631] Some machines don't have /opt/qa updated
https://bugzilla.redhat.com/show_bug.cgi?id=1350631 --- Comment #4 from Nigel Babu --- I actually noticed this on slave22 right now. There was no effect of git pull on the folder. I tried to rm -r /opt/qa and do a fresh git clone. The rm worked, the fresh clone didn't work. [root@slave22 opt]# git clone https://github.com/gluster/glusterfs-patch-acceptance-tests.git qa Cloning into 'qa'... [root@slave22 opt]# ls -l total 0 -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=Md4pP0wqUR&a=cc_unsubscribe ___ Gluster-infra mailing list Gluster-infra@gluster.org http://www.gluster.org/mailman/listinfo/gluster-infra
Re: [Gluster-infra] Renaming the log files for regression runs
On Tue, Aug 2, 2016 at 1:59 AM, Nigel Babu wrote: > Hello, > > Nithya suggested we rename the log files to have the Jenkins Job ID, making it > easier to match the log file to the job. I think this is a good idea and I'm > going to make the code changes. > > Does anyone have a reason *not* to do this? +1 to do this. Looks like a good enhancement to me. Thanks, Vijay ___ Gluster-infra mailing list Gluster-infra@gluster.org http://www.gluster.org/mailman/listinfo/gluster-infra
[Gluster-infra] [Bug 1362465] Bugzilla bot account required
https://bugzilla.redhat.com/show_bug.cgi?id=1362465 --- Comment #4 from Kaushal --- 2 already works. You just need to set a default CC, which is already done. -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=bEXUN2cy5a&a=cc_unsubscribe ___ Gluster-infra mailing list Gluster-infra@gluster.org http://www.gluster.org/mailman/listinfo/gluster-infra
[Gluster-infra] [Bug 1362465] Bugzilla bot account required
https://bugzilla.redhat.com/show_bug.cgi?id=1362465 --- Comment #3 from Nigel Babu --- I'm guessing we need two things here: 1) A bot account to change status and has bugzilla privileges to make changes. 2) An account that will forward bugs to a mailing list? I'm going to exclusively focus on 1). That account will not send email publicly. It will make changes. Remember we need to grant this bug editbugs privileges, so I'll have to talk to bugzilla ops folks and take their suggestions on what works best. -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=A7y5otojYZ&a=cc_unsubscribe ___ Gluster-infra mailing list Gluster-infra@gluster.org http://www.gluster.org/mailman/listinfo/gluster-infra
[Gluster-infra] [Bug 1355931] not able to git pull the source
https://bugzilla.redhat.com/show_bug.cgi?id=1355931 Nigel Babu changed: What|Removed |Added Status|VERIFIED|CLOSED Resolution|--- |CURRENTRELEASE Last Closed||2016-08-02 08:26:48 -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=jRoZ3NlTLc&a=cc_unsubscribe ___ Gluster-infra mailing list Gluster-infra@gluster.org http://www.gluster.org/mailman/listinfo/gluster-infra
[Gluster-infra] [Bug 1362465] Bugzilla bot account required
https://bugzilla.redhat.com/show_bug.cgi?id=1362465 --- Comment #2 from Kaushal --- (In reply to Niels de Vos from comment #1) > Please use the b...@gluster.org address (public mailinglist) for this. This doesn't seem a good idea to me. We can't be using a public mailing list for creating the bot account. For the bot account my preference is to create a bug...@gluster.org email (or an alias forwarding to the infra admins) and use it. -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=b0wErVGLNf&a=cc_unsubscribe ___ Gluster-infra mailing list Gluster-infra@gluster.org http://www.gluster.org/mailman/listinfo/gluster-infra
[Gluster-infra] [Bug 1362465] Bugzilla bot account required
https://bugzilla.redhat.com/show_bug.cgi?id=1362465 --- Comment #1 from Niels de Vos --- Please use the b...@gluster.org address (public mailinglist) for this. -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=1YbkXiA6mP&a=cc_unsubscribe ___ Gluster-infra mailing list Gluster-infra@gluster.org http://www.gluster.org/mailman/listinfo/gluster-infra
[Gluster-infra] [Bug 1362471] Jenkins should only assign one concurrent job per node
https://bugzilla.redhat.com/show_bug.cgi?id=1362471 Muthu Vigneshwaran changed: What|Removed |Added Keywords||Triaged Priority|unspecified |medium Status|NEW |ASSIGNED CC||mvign...@redhat.com Assignee|b...@gluster.org|nig...@redhat.com Severity|unspecified |medium -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=DYh9LyUVGR&a=cc_unsubscribe ___ Gluster-infra mailing list Gluster-infra@gluster.org http://www.gluster.org/mailman/listinfo/gluster-infra
[Gluster-infra] [Bug 1362465] Bugzilla bot account required
https://bugzilla.redhat.com/show_bug.cgi?id=1362465 Manikandan changed: What|Removed |Added Keywords||Triaged Priority|unspecified |medium Status|NEW |ASSIGNED CC||mselv...@redhat.com Assignee|b...@gluster.org|nig...@redhat.com Severity|unspecified |low -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=kC9gogOznP&a=cc_unsubscribe ___ Gluster-infra mailing list Gluster-infra@gluster.org http://www.gluster.org/mailman/listinfo/gluster-infra
Re: [Gluster-infra] Can I update /opt/qa for NetBSD?
On Tue, Aug 02, 2016 at 03:50:41PM +0530, Nigel Babu wrote: > We have quite a lot of local changes. I'm working on merging that into our > repo. If anyone is curious, the pull request is here: > > https://github.com/gluster/glusterfs-patch-acceptance-tests/pull/47 > Hi Emmanuel, Can you help me understand some of these changes? * A bunch of cleanup scripts are in build.sh. I think they can move into the Jenkins job itself. That's what we do for linux boxes. * Some test files have been made to 0644. Is this relevant or are these accidental changes? * Can the Python path and stuff be declared before the build.sh script is called in the Jenkins script? I don't know if this will work, I'll have to test. * I think we now have a standard way of skipping tests in the test runner itself rather than deleting the tests from the checkout. If not, I'll drive these fixes. * The check for whether there's two jobs assigned to the same machine can be controlled from Jenkins and I plan to do that, so we can probably remove that code as well. Does this sound okay? -- nigelb ___ Gluster-infra mailing list Gluster-infra@gluster.org http://www.gluster.org/mailman/listinfo/gluster-infra
Re: [Gluster-infra] Can I update /opt/qa for NetBSD?
On Tue, Aug 02, 2016 at 09:43:30AM +0200, Niels de Vos wrote: > On Tue, Aug 02, 2016 at 12:08:03PM +0530, Nigel Babu wrote: > > Hello folks, > > > > The /opt/qa folder on NetBSD nodes are on quite an old commit[1]. This means > > the URL to the logs and cores do not work. The script in master generates > > the > > correct URL. Is it safe to update this repo to the latest git master? > > I dont know. Just make sure there are no local modifications and record > the current commit-id that is used. It should be easy to revert in case > errors pop up. > > HTH, > Niels > > > > > > [1]: > > https://github.com/gluster/glusterfs-patch-acceptance-tests/commit/931157d3db4c48a985c3874c2d4ccf2ebb2fbd5f > > > > -- > > nigelb > > ___ > > Gluster-infra mailing list > > Gluster-infra@gluster.org > > http://www.gluster.org/mailman/listinfo/gluster-infra We have quite a lot of local changes. I'm working on merging that into our repo. If anyone is curious, the pull request is here: https://github.com/gluster/glusterfs-patch-acceptance-tests/pull/47 -- nigelb ___ Gluster-infra mailing list Gluster-infra@gluster.org http://www.gluster.org/mailman/listinfo/gluster-infra
[Gluster-infra] [Bug 1362471] New: Jenkins should only assign one concurrent job per node
https://bugzilla.redhat.com/show_bug.cgi?id=1362471 Bug ID: 1362471 Summary: Jenkins should only assign one concurrent job per node Product: GlusterFS Version: mainline Component: project-infrastructure Assignee: b...@gluster.org Reporter: nig...@redhat.com CC: b...@gluster.org, gluster-infra@gluster.org We currently have concurrent: yes for most jobs, because if we didn't it wouldn't run two jobs simultaneously on multiple machines. While we want concurrency, we also do not want two jobs on the same machine. The key is to use this: http://docs.openstack.org/infra/jenkins-job-builder/properties.html#properties.slave-utilization -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=fLNF541Xfo&a=cc_unsubscribe ___ Gluster-infra mailing list Gluster-infra@gluster.org http://www.gluster.org/mailman/listinfo/gluster-infra
[Gluster-infra] [Bug 1362465] New: Bugzilla bot account required
https://bugzilla.redhat.com/show_bug.cgi?id=1362465 Bug ID: 1362465 Summary: Bugzilla bot account required Product: GlusterFS Version: mainline Component: project-infrastructure Assignee: b...@gluster.org Reporter: kaus...@redhat.com CC: b...@gluster.org, gluster-infra@gluster.org Currently, review.gluster.org comments to bugzilla are done using Vijay's account (it was Avati's earlier). A bugzilla bot account needs to be used for this instead. -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=lVnK69Evpp&a=cc_unsubscribe ___ Gluster-infra mailing list Gluster-infra@gluster.org http://www.gluster.org/mailman/listinfo/gluster-infra
Re: [Gluster-infra] Can I update /opt/qa for NetBSD?
On Tue, Aug 02, 2016 at 12:08:03PM +0530, Nigel Babu wrote: > Hello folks, > > The /opt/qa folder on NetBSD nodes are on quite an old commit[1]. This means > the URL to the logs and cores do not work. The script in master generates the > correct URL. Is it safe to update this repo to the latest git master? I dont know. Just make sure there are no local modifications and record the current commit-id that is used. It should be easy to revert in case errors pop up. HTH, Niels > > [1]: > https://github.com/gluster/glusterfs-patch-acceptance-tests/commit/931157d3db4c48a985c3874c2d4ccf2ebb2fbd5f > > -- > nigelb > ___ > Gluster-infra mailing list > Gluster-infra@gluster.org > http://www.gluster.org/mailman/listinfo/gluster-infra signature.asc Description: PGP signature ___ Gluster-infra mailing list Gluster-infra@gluster.org http://www.gluster.org/mailman/listinfo/gluster-infra
[Gluster-infra] [Bug 1362368] Standardize timezone across all machines
https://bugzilla.redhat.com/show_bug.cgi?id=1362368 Michael Scherer changed: What|Removed |Added CC||m...@zarb.org --- Comment #1 from Michael Scherer --- Fine by me. I propose to make a external timezone role in ansible, that will abstract the difference between os. -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=zBodJzCVaW&a=cc_unsubscribe ___ Gluster-infra mailing list Gluster-infra@gluster.org http://www.gluster.org/mailman/listinfo/gluster-infra