[Gluster-infra] [Bug 1354705] New: Decomission sonarqube machine on Rackspace

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1354705

Bug ID: 1354705
   Summary: Decomission sonarqube machine on Rackspace
   Product: GlusterFS
   Version: mainline
 Component: project-infrastructure
  Keywords: Triaged
  Assignee: b...@gluster.org
  Reporter: nig...@redhat.com
CC: b...@gluster.org, gluster-infra@gluster.org



Please decommission sonarqube machine on Rackspace. Confirmed with semiosis on
IRC.

< semiosis> nigelb: the only sonarqube i'm familiar with is the one i set up
for glusterfs-java-filesystem.  is that what you're talking about?
< nigelb> semiosis: yep!
< semiosis> nigelb: how can I help you?
< nigelb> semiosis: do we use the instance?
< nigelb> (I'm cleaning up rackspace machines pretty thoroughly)
< semiosis> you can decommission it
< nigelb> excellent, thank you.
< semiosis> it hosted code quality reports for this project,
https://github.com/semiosis/glusterfs-java-filesystem, but the links are dead
now.

-- 
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=zjwgdRHFuv=cc_unsubscribe
___
Gluster-infra mailing list
Gluster-infra@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-infra

[Gluster-infra] [Bug 1354529] New: compare-bug-version-and-git-branch failing for seemingly no reason

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1354529

Bug ID: 1354529
   Summary: compare-bug-version-and-git-branch failing for
seemingly no reason
   Product: GlusterFS
   Version: mainline
 Component: project-infrastructure
  Keywords: Triaged
  Priority: urgent
  Assignee: nig...@redhat.com
  Reporter: nig...@redhat.com
CC: b...@gluster.org, gluster-infra@gluster.org



 ndevos, nigelb  There is a weird issue - one patch is reporting
smoke test error due to another bug 1349657
 Bug https://bugzilla.redhat.com:443/show_bug.cgi?id=1349657 low,
unspecified, ---, johnzzpcrystal, MODIFIED , process glusterd set
TCP_USER_TIMEOUT failed
 ndevos, I can see you have changed the status of 1349657 to
MODIFIED :)
 ndevos, nigelb  http://review.gluster.org/#/c/14830/   -
https://build.gluster.org/job/compare-bug-version-and-git-branch/19263/console
 Saravanakmr: yeah, the patch for that has been merged?
 ndarshan, yes it is merged
 ndevos, yes it is merged but seeing issue in another patch
 ndarshan, sorry..ignore
 Saravanakmr: hmm, right, the other patch is for bug 1351071
 Bug https://bugzilla.redhat.com:443/show_bug.cgi?id=1351071
medium, unspecified, ---, sarumuga, ASSIGNED , [geo-rep] Stopped geo-rep
session gets started automatically once all the master nodes are upgraded
 ndevos, weird !
 Saravanakmr: I have no idea why that could happen :-/
 nigelb, can you please have a look?
 nigelb, ndevos another patch from Aravinda also fails with same
reason http://review.gluster.org/#/c/14627/
 Saravanakmr: oh, that actually is the same commit-id, and the commit
message is used to parse the BUG:
 One of my patches too ran into same issue  -
https://build.gluster.org/job/compare-bug-version-and-git-branch/19265/console
 nigelb, ndevos , Saravanakmr ^^^
 skoduri: is that also doing a "Checking out Revision
b2c73cbf423de6201f956f522b7429615c88869d (origin/master)" ?
 ndevos, yes
 ndevos, and from http://review.gluster.org/#/c/14878/3, looks like
that was parent commiID
 hmm, maybe nigelb updated the Jenkins job to the new Jenkins Job
Builder configuration and some option or something was missed?
 okay
 obviously there was an update to the new .yml file 2 hours ago, not
sure if that goes live automatically

https://github.com/gluster/glusterfs-patch-acceptance-tests/blob/master/jenkins/jobs/compare-bug-version-and-git-branch.yml
for the curious, but I have no idea what options are needed or how it releates
to other config
 nigelb: the compare-bug-version-and-git-branch script expects the
to-test change to be checked out, not sure if the JJB config does that?

-- 
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=LFSjoJjXen=cc_unsubscribe
___
Gluster-infra mailing list
Gluster-infra@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-infra

[Gluster-infra] Jenkins results for devrpms 404ing

[Nigel Babu]

Hello folks,

A lot of older devrpm jobs will 404 because I was only saving 10 latest jobs.
I thought since we didn't consume the rpms, I could safely delete them. Turns
out we do want the logs. I've updated the job so we keep the last 50 jobs. This
won't fix the jobs that already 404, but at least it shouldn't happen anymore.

--
nigelb
___
Gluster-infra mailing list
Gluster-infra@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-infra

[Gluster-infra] [Bug 1354422] Regression tests do not set the right paths

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1354422

Nigel Babu  changed:

   What|Removed |Added

 CC||pguru...@redhat.com
  Flags||needinfo?(pgurusid@redhat.c
   ||om)



--- Comment #1 from Nigel Babu  ---
What should be the value for these variables?

-- 
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=NT8iL77xlo=cc_unsubscribe
___
Gluster-infra mailing list
Gluster-infra@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-infra

[Gluster-infra] [Bug 1354422] New: Regression tests do not set the right paths

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1354422

Bug ID: 1354422
   Summary: Regression tests do not set the right paths
   Product: GlusterFS
   Version: mainline
 Component: project-infrastructure
  Assignee: nig...@redhat.com
  Reporter: nig...@redhat.com
CC: b...@gluster.org, gluster-infra@gluster.org



For regression tests, we do not install glusterfs in the right path, so we need
to set the following paths: PKG_CONFIG_PATH, LIBRARY_PATH, C_INCLUDE_PATH.

This is causing the review in URL to fail.

-- 
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=ZJPSafdV6j=cc_unsubscribe
___
Gluster-infra mailing list
Gluster-infra@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-infra

[Gluster-infra] [Bug 1351626] Kill the inactive netbsd machines and bring up new ones

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1351626



--- Comment #1 from Nigel Babu  ---
The path of least resistance according to Emmanuel is to clone nbslave70.

misc, what's the process to assign domain names after I bring up new machines?
(That bit can probably be put directly on the docs.)

-- 
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=bDq2aNRnCb=cc_unsubscribe
___
Gluster-infra mailing list
Gluster-infra@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-infra