Re: [Gluster-infra] Smoke tests run on the builder in RH DC (at least)

[Michael Scherer]

Le lundi 25 janvier 2016 à 22:24 +0100, Niels de Vos a écrit :
> On Mon, Jan 25, 2016 at 06:59:33PM +0100, Michael Scherer wrote:
> > Hi,
> > 
> > so today, after fixing one last config item, the smoke test jobs run
> > fine on the Centos 6 builder in the RH DC, which build things as non
> > root, then start the tests, then reboot the server.
> 
> Nice, sounds like great progress!
> 
> Did you need to change anything in the build or test scripts under
> /opt/qa? If so, please make sure that the changes land in the
> repository:
> 
>   https://github.com/gluster/glusterfs-patch-acceptance-tests/

So far, I mostly removed code that was running on the jenkins script
(ie, the cleanup part that kill process), and added a reboot at the end.
Not sure I want to have that in the script :)

> > Now, I am looking at the fedora one, but once this one is good, I will
> > likely reinstall a few builders as a test, and go on Centos 7 builder.
> 
> I'm not sure yet if I made an error, or what is going on. But for some
> reason smoke tests for my patch series fails... This is the smoke result
> of the 1st patch in the serie, it only updates the fuse-header to a
> newer version. Of course local testing works just fine... The output and
> (not available) logs of the smoke test do not really help me :-/
> 
>   https://build.gluster.org/job/smoke/24395/console
> 
> Could this be related to the changes that were made? If not, I'd
> appreciate a pointer to my mistake.

No, I tested on a separate job to not interfere.

> > I was also planning to look at jenkins job builder for the jenkins, but
> > no time yet. Will be after jenkins migration to a new host (which is
> > still not planned, unlike gerrit where we should be attempting to find a
> > time for that)
> 
> We also might want to use Jenkins Job Builder for the tests we're adding
> to the CentOS CI. Maybe we could experiment with it there first, and
> then use our knowledge to the Gluster Jenkins?

Why not. I think it would work fine on our too, as i am not sure it need
to completely take over the server configuration.
-- 
Michael Scherer
Sysadmin, Community Infrastructure and Platform, OSAS




signature.asc
Description: This is a digitally signed message part
___
Gluster-infra mailing list
Gluster-infra@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-infra

[Gluster-infra] Gerrit down for 10 to 15 minutes for reindexing

[Michael Scherer]

Hi,

in order to fix some issues (I hope), I am gonna start a reindex of the
lucense DB of gerrit. This requires the server to be put offline for a
while, and I did a test on another VM, would take ~10 minutes (it was
240 seconds on the VM, but it was likely faster since the VM is faster)

I will to do that around 18h UTC, in ~ 3h ( so 1pm Boston time, 23h Pune
time, and 19h Amsterdam time, so it shouldn't impact too much people who
would either be sleeping and/or eating ). 

If people really want to work, we always have bugs to triage :)
-- 
Michael Scherer
Sysadmin, Community Infrastructure and Platform, OSAS




signature.asc
Description: This is a digitally signed message part
___
Gluster-infra mailing list
Gluster-infra@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-infra

Re: [Gluster-infra] [Gluster-devel] Jenkins accounts for all devs.

[Mohammed Rafi K C]

On 01/22/2016 11:31 AM, Ravishankar N wrote:
> On 01/14/2016 12:16 PM, Kaushal M wrote:
>> On Thu, Jan 14, 2016 at 10:33 AM, Raghavendra Talur
>>  wrote:
>>>
>>> On Thu, Jan 14, 2016 at 10:32 AM, Ravishankar N
>>> 
>>> wrote:
 On 01/08/2016 12:03 PM, Raghavendra Talur wrote:
> P.S: Stop using the "universal" jenkins account to trigger jenkins
> build
> if you are not a maintainer.
> If you are a maintainer and don't have your own jenkins account
> then get
> one soon!
>
 I would request for a jenkins account for non-maintainers too, at
 least
 for the devs who are actively contributing code (as opposed to random
 one-off commits from persons). That way, if the regression failure is
 *definitely* not in my patch (or) is a spurious failure (or) is
 something
 that I need to take a netbsd slave offline to debug etc.,  I don't
 have to
 be blocked on the Maintainer. Since the accounts are anyway tied to an
 individual, it should be easy to spot if someone habitually re-trigger
 regressions without any initial debugging.

>>> +1

+2 ;)

In the last couple of days, It has become painful procedure  to get one
patch merged upstream. Having an account for everyone will definitely
help here to some extend.

Regards
Rafi KC




>> We'd like to give everyone accounts. But the way we're providing
>> accounts now gives admin accounts to all. This is not very secure.
>>
>> This was one of the reasons misc setup freeipa.gluster.org, to provide
>> controlled accounts for all. But it hasn't been used yet. We would
>> need to integrate jenkins and the slaves with freeipa, which would
>> give everyone easy access.
>
> Hi Michael,
> Do you think it is possible to have this integration soon so that all
> contributors can re-trigger/initiate builds by themselves?
> Regards,
> Ravi
 -Ravi
>>>
>>>
>>> ___
>>> Gluster-devel mailing list
>>> gluster-de...@gluster.org
>>> http://www.gluster.org/mailman/listinfo/gluster-devel
>
>
> ___
> Gluster-devel mailing list
> gluster-de...@gluster.org
> http://www.gluster.org/mailman/listinfo/gluster-devel

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

[Gluster-infra] Smoke tests run on the builder in RH DC (at least)

[Michael Scherer]

Hi,

so today, after fixing one last config item, the smoke test jobs run
fine on the Centos 6 builder in the RH DC, which build things as non
root, then start the tests, then reboot the server.

Now, I am looking at the fedora one, but once this one is good, I will
likely reinstall a few builders as a test, and go on Centos 7 builder.

I was also planning to look at jenkins job builder for the jenkins, but
no time yet. Will be after jenkins migration to a new host (which is
still not planned, unlike gerrit where we should be attempting to find a
time for that)


-- 
Michael Scherer
Sysadmin, Community Infrastructure and Platform, OSAS




signature.asc
Description: This is a digitally signed message part
___
Gluster-infra mailing list
Gluster-infra@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-infra

Re: [Gluster-infra] [Gluster-Maintainers] Removed "clean workspace" step from NetBSD regression job

[Niels de Vos]

On Tue, Jan 26, 2016 at 02:36:52AM +0530, Raghavendra Talur wrote:
> Hi,
> 
> I have removed "clean workspace" from NetBSD regression job too. Vijay had
> earlier removed it from CentOS regression.
> Cleaning the workspace resulted in deletion of complete git repo and
> re-clone takes a lot of time. Gerrit trigger/Git plugin intelligently reset
> to HEAD~n when moving to next job and hence save time.

Ok, just update the xml file too:

  
https://github.com/gluster/glusterfs-patch-acceptance-tests/tree/master/jenkins/jobs

You can use https://build.gluster.org/cli/ with the "get-job" command.

Thanks,
Niels


signature.asc
Description: PGP signature
___
Gluster-infra mailing list
Gluster-infra@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-infra

[Gluster-infra] Removed "clean workspace" step from NetBSD regression job

[Raghavendra Talur]

Hi,

I have removed "clean workspace" from NetBSD regression job too. Vijay had
earlier removed it from CentOS regression.
Cleaning the workspace resulted in deletion of complete git repo and
re-clone takes a lot of time. Gerrit trigger/Git plugin intelligently reset
to HEAD~n when moving to next job and hence save time.

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

Re: [Gluster-infra] Enabling comment based trigger on jenkins

[Niels de Vos]

On Tue, Jan 26, 2016 at 02:13:14AM +0530, Raghavendra Talur wrote:
> Hi,
> 
> Prashanth informed about a simple way to let every contributor retrigger
> the regression runs that openstack uses.
> Contributor has to simply post "recheck no bug" as comment on the patch set.
> Read more here:
> http://zqfan.github.io/openstack/2014/01/03/what-should-i-do-when-jenkins-fails/
> 
> I tweaked it for gluster, enabled and tested it. Trigger comments are:
> 
> recheck netbsd
> recheck smoke
> recheck centos
> 
> If no one has any objections to this method(security implications
> included), then I would like to announce it on gluster-devel.

Sounds good to me! This should reduce the need for handing out Jenkins
accounts.

Thanks,
Niels


signature.asc
Description: PGP signature
___
Gluster-infra mailing list
Gluster-infra@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-infra

Re: [Gluster-infra] Enabling comment based trigger on jenkins

[Vijay Bellur]

- Original Message -
> From: "Niels de Vos" 
> To: "Raghavendra Talur" 
> Cc: "gluster-infra" 
> Sent: Monday, January 25, 2016 4:30:26 PM
> Subject: Re: [Gluster-infra] Enabling comment based trigger on jenkins
> 
> On Tue, Jan 26, 2016 at 02:13:14AM +0530, Raghavendra Talur wrote:
> > Hi,
> > 
> > Prashanth informed about a simple way to let every contributor retrigger
> > the regression runs that openstack uses.
> > Contributor has to simply post "recheck no bug" as comment on the patch
> > set.
> > Read more here:
> > http://zqfan.github.io/openstack/2014/01/03/what-should-i-do-when-jenkins-fails/
> > 
> > I tweaked it for gluster, enabled and tested it. Trigger comments are:
> > 
> > recheck netbsd
> > recheck smoke
> > recheck centos
> > 
> > If no one has any objections to this method(security implications
> > included), then I would like to announce it on gluster-devel.
> 
> Sounds good to me! This should reduce the need for handing out Jenkins
> accounts.
> 

+1.

Thank you Raghavendra for doing this!

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

Re: [Gluster-infra] [Gluster-devel] Smoke tests run on the builder in RH DC (at least)

[Niels de Vos]

On Mon, Jan 25, 2016 at 10:24:33PM +0100, Niels de Vos wrote:
> On Mon, Jan 25, 2016 at 06:59:33PM +0100, Michael Scherer wrote:
> > Hi,
> > 
> > so today, after fixing one last config item, the smoke test jobs run
> > fine on the Centos 6 builder in the RH DC, which build things as non
> > root, then start the tests, then reboot the server.
> 
> Nice, sounds like great progress!
> 
> Did you need to change anything in the build or test scripts under
> /opt/qa? If so, please make sure that the changes land in the
> repository:
> 
>   https://github.com/gluster/glusterfs-patch-acceptance-tests/
> 
> > Now, I am looking at the fedora one, but once this one is good, I will
> > likely reinstall a few builders as a test, and go on Centos 7 builder.
> 
> I'm not sure yet if I made an error, or what is going on. But for some
> reason smoke tests for my patch series fails... This is the smoke result
> of the 1st patch in the serie, it only updates the fuse-header to a
> newer version. Of course local testing works just fine... The output and
> (not available) logs of the smoke test do not really help me :-/
> 
>   https://build.gluster.org/job/smoke/24395/console
> 
> Could this be related to the changes that were made? If not, I'd
> appreciate a pointer to my mistake.

Well, I guess that this is a limitation in the FUSE kernel module that
is part of EL6 and EL7. One of the structures sent is probably too big
and the kernel refuses to accept it. I guess I'll need to go back to the
drawing board and add a real check for the FUSE version, or something
like that.

Niels


signature.asc
Description: PGP signature
___
Gluster-infra mailing list
Gluster-infra@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-infra

[Gluster-infra] [Bug 1291537] [RFE] Provide mechanism to spin up reproducible test environment for all developers

[bugzilla]

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



--- Comment #8 from Vijay Bellur  ---
REVIEW: http://review.gluster.org/13251 (vagrant-test: Use pre-baked box for
better perf) posted (#2) for review on master by Raghavendra Talur
(rta...@redhat.com)

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