Re: [Gluster-devel] rackspace-netbsd7-regression-triggered has been disabled
Openstack uses Zuul [1], which manages this kinds of issues. Maybe we can explore it. This was brought up sometime before by Prashant Pai (I don't remember if it was on IRC or here). ~kaushal [1] http://ci.openstack.org/zuul/ ___ Gluster-devel mailing list Gluster-devel@gluster.org http://www.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] rackspace-netbsd7-regression-triggered has been disabled
On Wed, Apr 01, 2015 at 12:50:30PM +0530, Vijay Bellur wrote: I think all we need is to create another gerrit user like NetBSD Regression or so and have verified votes routed through this user. Just as multiple users can provide distinct CR votes, we can have multiple build systems provide distinct Verified votes. Yes, plase do that: a nb7build user like we have a build user. It can have the same .ssh/authorized_keys as build user. -- Emmanuel Dreyfus m...@netbsd.org ___ Gluster-devel mailing list Gluster-devel@gluster.org http://www.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] rackspace-netbsd7-regression-triggered has been disabled
On 04/01/2015 09:42 AM, Justin Clift wrote: On 1 Apr 2015, at 05:04, Emmanuel Dreyfus m...@netbsd.org wrote: Justin Clift jus...@gluster.org wrote: That, or perhaps we could have two verified fields? Sure. Whichever works. :) Personally, I'm not sure how to do either yet. In http://build.gluster.org/gerrit-trigger/ you have Verdict categories with CRVW (code review) and VRIF (verified), and there is a add verdict category, which suggest this is something that can be done. Of course the Gerrit side will need some configuration too, but if Jenkins can deal with more Gerrit fields, there must be a way to add fields in Gerrit. Interesting. Marcelo, this sounds like something you'd know about. Any ideas? :) We're trying to add an extra Verified column to our Gerrit + Jenkins setup. We have an existing one for Gluster Build System (which is our CentOS Regression testing). Now we want to add one for our NetBSD Regression testing. I think all we need is to create another gerrit user like NetBSD Regression or so and have verified votes routed through this user. Just as multiple users can provide distinct CR votes, we can have multiple build systems provide distinct Verified votes. I don't think we need an extra column here. -Vijay ___ Gluster-devel mailing list Gluster-devel@gluster.org http://www.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] rackspace-netbsd7-regression-triggered has been disabled
On 1 Apr 2015, at 17:20, Marcelo Barbosa fireman...@fedoraproject.org wrote: yep, using on Jenkins the plugin Gerrit Trigger, this plugin trigger all requests for all repositories and all branches, this function running with Auto QA tests and vote with ACL verified, for example: https://gerrit.ovirt.org/#/c/37886/ my intention is make one deploy with one complete example the use this, comming soon :D We already use the Gerrit Trigger plugin extensively. :) Now we need to get more advanced with it... In our existing setup, we have bunch of fast tests that run automatically (triggered), and which vote. We use this for initial smoke testing to locate (fail on) obviously problems quickly. We also have a much more in-depth CentOS 6.x regression test (~2hours run time) that's triggered. It doesn't vote using the Gerrit trigger method. Instead it calls back via ssh to Gerrit, indicating SUCCESS or FAILURE. That status goes into a column in the Gerrit CR, to show if it passed the regression test or not. Now... we have a NetBSD 7.x regression test (~2 hour run time) that's also triggered. We need to find a way for this to communicate back to Gerrit. We've tried using the same method used for our CentOS 6.x communication back, but the status results for the NetBSD tests conflict with the CentOS status results. We need some kind of solution. Hoping you have ideas? :) We're ok with pretty much anything that works and can be setup ASAP. Like today. :) + Justin -- GlusterFS - http://www.gluster.org An open source, distributed file system scaling to several petabytes, and handling thousands of clients. My personal twitter: twitter.com/realjustinclift ___ Gluster-devel mailing list Gluster-devel@gluster.org http://www.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] rackspace-netbsd7-regression-triggered has been disabled
yep, using on Jenkins the plugin Gerrit Trigger, this plugin trigger all requests for all repositories and all branches, this function running with Auto QA tests and vote with ACL verified, for example: https://gerrit.ovirt.org/#/c/37886/ my intention is make one deploy with one complete example the use this, comming soon :D firemanxbr On Wed, Apr 1, 2015 at 4:32 AM, Emmanuel Dreyfus m...@netbsd.org wrote: On Wed, Apr 01, 2015 at 12:50:30PM +0530, Vijay Bellur wrote: I think all we need is to create another gerrit user like NetBSD Regression or so and have verified votes routed through this user. Just as multiple users can provide distinct CR votes, we can have multiple build systems provide distinct Verified votes. Yes, plase do that: a nb7build user like we have a build user. It can have the same .ssh/authorized_keys as build user. -- Emmanuel Dreyfus m...@netbsd.org ___ Gluster-devel mailing list Gluster-devel@gluster.org http://www.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] rackspace-netbsd7-regression-triggered has been disabled
Justin Clift jus...@gluster.org wrote: What about ading another nb7build user in gerrit? That way results will not conflict. I'm not sure. What makes you doubt? When multiple user cast votes, they do not overide each others? -- Emmanuel Dreyfus http://hcpnet.free.fr/pubz m...@netbsd.org ___ Gluster-devel mailing list Gluster-devel@gluster.org http://www.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] rackspace-netbsd7-regression-triggered has been disabled
Justin Clift jus...@gluster.org wrote: We need some kind of solution. What about ading another nb7build user in gerrit? That way results will not conflict. -- Emmanuel Dreyfus http://hcpnet.free.fr/pubz m...@netbsd.org ___ Gluster-devel mailing list Gluster-devel@gluster.org http://www.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] rackspace-netbsd7-regression-triggered has been disabled
believe that this problem may be with the version of the old Gerrit, because I Gerrit in 2.10.2 version and Jenkins in 1.596.1 and squeegee build tests that take up to 96 hours in codesonar and return the voting Gerrit verified +1 or -1. firemanxbr On Wed, Apr 1, 2015 at 1:38 PM, Emmanuel Dreyfus m...@netbsd.org wrote: Justin Clift jus...@gluster.org wrote: We need some kind of solution. What about ading another nb7build user in gerrit? That way results will not conflict. -- Emmanuel Dreyfus http://hcpnet.free.fr/pubz m...@netbsd.org ___ Gluster-devel mailing list Gluster-devel@gluster.org http://www.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] rackspace-netbsd7-regression-triggered has been disabled
On 1 Apr 2015, at 17:38, Emmanuel Dreyfus m...@netbsd.org wrote: Justin Clift jus...@gluster.org wrote: We need some kind of solution. What about ading another nb7build user in gerrit? That way results will not conflict. I'm not sure. However, Vijay's now added me as an admin in our production Gerrit instalce, and I have the process for restoring our backups in a local VM (on my desktop) worked out now. So... I can test this tomorrow morning and try it out. Then we'll know for sure. :) + Justin -- GlusterFS - http://www.gluster.org An open source, distributed file system scaling to several petabytes, and handling thousands of clients. My personal twitter: twitter.com/realjustinclift ___ Gluster-devel mailing list Gluster-devel@gluster.org http://www.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] rackspace-netbsd7-regression-triggered has been disabled
On 1 Apr 2015, at 03:03, Emmanuel Dreyfus m...@netbsd.org wrote: Jeff Darcy jda...@redhat.com wrote: That's fine. I left a note for you in the script, regarding what I think it needs to do at that point. Here is the comment: # We shouldn't be touching CR at all. For V, we should set V+1 iff this # test succeeded *and* the value was already 0 or 1, V-1 otherwise. I # don't know how to do that, but the various smoke tests must be doing # something similar/equivalent. It's also possible that this part should # be done as a post-build action instead. The problem is indeed that we do now know how to retreive previous V value. I guess gerrit is the place where V combinations should be correctly handled. What is the plan for NetBSD regression now? It will fail anything which has not been rebased after recent fixes were merged, but apart from that the thing is in rather good shape right now. It sounds like we need a solution to have both the NetBSD and CentOS regressions run, and only give the +1 when both of them have successfully finished. If either of them fail, then it gets a -1. Research time. ;) + Justin -- GlusterFS - http://www.gluster.org An open source, distributed file system scaling to several petabytes, and handling thousands of clients. My personal twitter: twitter.com/realjustinclift ___ Gluster-devel mailing list Gluster-devel@gluster.org http://www.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] rackspace-netbsd7-regression-triggered has been disabled
Jeff Darcy jda...@redhat.com wrote: That's fine. I left a note for you in the script, regarding what I think it needs to do at that point. Here is the comment: # We shouldn't be touching CR at all. For V, we should set V+1 iff this # test succeeded *and* the value was already 0 or 1, V-1 otherwise. I # don't know how to do that, but the various smoke tests must be doing # something similar/equivalent. It's also possible that this part should # be done as a post-build action instead. The problem is indeed that we do now know how to retreive previous V value. I guess gerrit is the place where V combinations should be correctly handled. What is the plan for NetBSD regression now? It will fail anything which has not been rebased after recent fixes were merged, but apart from that the thing is in rather good shape right now. -- Emmanuel Dreyfus http://hcpnet.free.fr/pubz m...@netbsd.org ___ Gluster-devel mailing list Gluster-devel@gluster.org http://www.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] rackspace-netbsd7-regression-triggered has been disabled
On 1 Apr 2015, at 04:07, Emmanuel Dreyfus m...@netbsd.org wrote: Justin Clift jus...@gluster.org wrote: It sounds like we need a solution to have both the NetBSD and CentOS regressions run, and only give the +1 when both of them have successfully finished. If either of them fail, then it gets a -1. That, or perhaps we could have two verified fields? Sure. Whichever works. :) Personally, I'm not sure how to do either yet. + Justin -- GlusterFS - http://www.gluster.org An open source, distributed file system scaling to several petabytes, and handling thousands of clients. My personal twitter: twitter.com/realjustinclift ___ Gluster-devel mailing list Gluster-devel@gluster.org http://www.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] rackspace-netbsd7-regression-triggered has been disabled
On 1 Apr 2015, at 05:04, Emmanuel Dreyfus m...@netbsd.org wrote: Justin Clift jus...@gluster.org wrote: That, or perhaps we could have two verified fields? Sure. Whichever works. :) Personally, I'm not sure how to do either yet. In http://build.gluster.org/gerrit-trigger/ you have Verdict categories with CRVW (code review) and VRIF (verified), and there is a add verdict category, which suggest this is something that can be done. Of course the Gerrit side will need some configuration too, but if Jenkins can deal with more Gerrit fields, there must be a way to add fields in Gerrit. Interesting. Marcelo, this sounds like something you'd know about. Any ideas? :) We're trying to add an extra Verified column to our Gerrit + Jenkins setup. We have an existing one for Gluster Build System (which is our CentOS Regression testing). Now we want to add one for our NetBSD Regression testing. Regards and best wishes, Justin Clift -- GlusterFS - http://www.gluster.org An open source, distributed file system scaling to several petabytes, and handling thousands of clients. My personal twitter: twitter.com/realjustinclift ___ Gluster-devel mailing list Gluster-devel@gluster.org http://www.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] rackspace-netbsd7-regression-triggered has been disabled
Justin Clift jus...@gluster.org wrote: It sounds like we need a solution to have both the NetBSD and CentOS regressions run, and only give the +1 when both of them have successfully finished. If either of them fail, then it gets a -1. That, or perhaps we could have two verified fields? -- Emmanuel Dreyfus http://hcpnet.free.fr/pubz m...@netbsd.org ___ Gluster-devel mailing list Gluster-devel@gluster.org http://www.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] rackspace-netbsd7-regression-triggered has been disabled
Justin Clift jus...@gluster.org wrote: That, or perhaps we could have two verified fields? Sure. Whichever works. :) Personally, I'm not sure how to do either yet. In http://build.gluster.org/gerrit-trigger/ you have Verdict categories with CRVW (code review) and VRIF (verified), and there is a add verdict category, which suggest this is something that can be done. Of course the Gerrit side will need some configuration too, but if Jenkins can deal with more Gerrit fields, there must be a way to add fields in Gerrit. -- Emmanuel Dreyfus http://hcpnet.free.fr/pubz m...@netbsd.org ___ Gluster-devel mailing list Gluster-devel@gluster.org http://www.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] rackspace-netbsd7-regression-triggered has been disabled
The following Gerrit patchsets were affected: http://review.gluster.org/#/c/9557/ (Nandaja Varma) changelog: Fixing buffer overrun coverity issues http://review.gluster.org/#/c/9981/ (Pranith Kumar Karampuri) cluster/ec: Refactor inode-writev http://review.gluster.org/#/c/9970/ (Kotresh HR) extras: Fix stop-all-gluster-processes.sh script http://review.gluster.org/#/c/10075/ (Jeff Darcy) socket: use OpenSSL multi-threading interfaces this one nuked a CR+1 (from Kaleb) as well as V+1 In the absence of any other obvious way to fix this up, I'll start new jobs for these momentarily. ___ Gluster-devel mailing list Gluster-devel@gluster.org http://www.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] rackspace-netbsd7-regression-triggered has been disabled
The following Gerrit patchsets were affected: http://review.gluster.org/#/c/9557/ (Nandaja Varma) changelog: Fixing buffer overrun coverity issues http://review.gluster.org/#/c/9981/ (Pranith Kumar Karampuri) cluster/ec: Refactor inode-writev http://review.gluster.org/#/c/9970/ (Kotresh HR) extras: Fix stop-all-gluster-processes.sh script http://review.gluster.org/#/c/10075/ (Jeff Darcy) socket: use OpenSSL multi-threading interfaces this one nuked a CR+1 (from Kaleb) as well as V+1 In the absence of any other obvious way to fix this up, I'll start new jobs for these momentarily. Found another one: http://review.gluster.org/#/c/9859/ (Raghavendra Talur) libglusterfs/syncop: Add xdata to all syncop calls Started a new job for that one too. ___ Gluster-devel mailing list Gluster-devel@gluster.org http://www.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] rackspace-netbsd7-regression-triggered has been disabled
On 1 Apr 2015, at 00:48, Jeff Darcy jda...@redhat.com wrote: The following Gerrit patchsets were affected: http://review.gluster.org/#/c/9557/ (Nandaja Varma) changelog: Fixing buffer overrun coverity issues http://review.gluster.org/#/c/9981/ (Pranith Kumar Karampuri) cluster/ec: Refactor inode-writev http://review.gluster.org/#/c/9970/ (Kotresh HR) extras: Fix stop-all-gluster-processes.sh script http://review.gluster.org/#/c/10075/ (Jeff Darcy) socket: use OpenSSL multi-threading interfaces this one nuked a CR+1 (from Kaleb) as well as V+1 In the absence of any other obvious way to fix this up, I'll start new jobs for these momentarily. Found another one: http://review.gluster.org/#/c/9859/ (Raghavendra Talur) libglusterfs/syncop: Add xdata to all syncop calls Started a new job for that one too. If you have a build.gluster.org login, fixing this is pretty simple. Doesn't need the job to be re-run. ;) All you need to do is change to the jenkins user (on build.gluster.org) then run the command that's at the bottom of the regression test run. For example, looking at the regression run for the first issue you have in the list: http://build.gluster.org/job/rackspace-regression-2GB-triggered/6198/consoleFull At the very end of the regression run, it shows this: ssh bu...@review.gluster.org gerrit review --message ''\''http://build.gluster.org/job/rackspace-regression-2GB-triggered/6198/consoleFull : SUCCESS'\''' --project=glusterfs --verified=+1 --code-review=0 ab9bdb54f89a6f8080f8b338b32b23698e9de515 Running that command from the jenkins user on build.gluster.org resend the SUCCESS message to Gerrit: [homepc]$ ssh build.gluster.org [justin@build]$ sudo su - jenkins [jenkins@build]$ ssh bu...@review.gluster.org gerrit review --message ''\''http://build.gluster.org/job/rackspace-regression-2GB-triggered/6198/consoleFull : SUCCESS'\''' --project=glusterfs --verified=+1 --code-review=0 ab9bdb54f89a6f8080f8b338b32b23698e9de515 [jenkins@build]$ And it's done. ;) I've done the first one. I'll leave the others for you, so you embed the skill :) Regards and best wishes, Justin Clift -- GlusterFS - http://www.gluster.org An open source, distributed file system scaling to several petabytes, and handling thousands of clients. My personal twitter: twitter.com/realjustinclift ___ Gluster-devel mailing list Gluster-devel@gluster.org http://www.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] rackspace-netbsd7-regression-triggered has been disabled
I've done the first one. I'll leave the others for you, so you embed the skill :) Done. Thanks! I also canceled the now-superfluous jobs. Maybe in my Copious Spare Time(tm) I'll write a script to do this more easily for other obviously-spurious regression results. ___ Gluster-devel mailing list Gluster-devel@gluster.org http://www.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] rackspace-netbsd7-regression-triggered has been disabled
Jeff Darcy jda...@redhat.com wrote: http://review.gluster.org/#/c/9970/ (Kotresh HR) extras: Fix stop-all-gluster-processes.sh script Theses are the NetBSD regression failures for which we got fixes merged recently. Doesn't it just need to be rebased? I re-enabled NetBSD regression, with voting disabled until the mess is fixed. -- Emmanuel Dreyfus http://hcpnet.free.fr/pubz m...@netbsd.org ___ Gluster-devel mailing list Gluster-devel@gluster.org http://www.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] rackspace-netbsd7-regression-triggered has been disabled
http://review.gluster.org/#/c/9970/ (Kotresh HR) extras: Fix stop-all-gluster-processes.sh script Theses are the NetBSD regression failures for which we got fixes merged recently. Doesn't it just need to be rebased? Quite possibly. I wasn't looking at patch contents all that closely. I re-enabled NetBSD regression, with voting disabled until the mess is fixed. That's fine. I left a note for you in the script, regarding what I think it needs to do at that point. ___ Gluster-devel mailing list Gluster-devel@gluster.org http://www.gluster.org/mailman/listinfo/gluster-devel
