On Sat, May 30, 2015 at 08:24:31AM +0530, Pranith Kumar Karampuri wrote: > > > On 05/30/2015 08:06 AM, Atin Mukherjee wrote: > > > > > >On 30 May 2015 07:54, "Pranith Kumar Karampuri" <pkarampu@xxxxxxxxxx > ><mailto:pkarampu@xxxxxxxxxx>> wrote: > >> > >> > >> > >> On 05/30/2015 07:44 AM, Pranith Kumar Karampuri wrote: > >>> > >>> > >>> > >>> On 05/30/2015 07:33 AM, Nagaprasad Sathyanarayana wrote: > >>>> > >> > >>> It appears to me that glusterd-errno.h was added in the patch > >http://review.gluster.org/10313, which was merged on 29th. Please correct > >me if I am wrong. > >I think we should seggregate votes for regression and the other set of > >jobs which checks for the sanity of the patch including devrpm build. The > >reason this patch got into the codebase was reviewers saw both linux and > >netbsd regressions voted +1, but the other set of job was not run by that > >time. Having a separate vote might help here. Off late, we have also seen > >that regression and smoke can override their votes which is also not > >correct. Thoughts? > > > I think giving smoke tests different voter-id would help. We can check for 3 > acks from Gluster Build System, NetBSD and may be Smoke/RPM Build system and > then merge. I see smoke as an extreme minimal sanity test. And I think we should not start regression tests before smoke/rpmbuild has passed. Does that sound acceptible too? Niels > > Pranith > > > >>> > >>> I think it is supposed to be added to Makefile as well. Let me do some > >testing. > >> > >> http://review.gluster.org/11010 fixes this. > >> > >> Thanks a lot Naga :-) > >> > >> Pranith > >> > >>> > >>> Pranith > >>>> > >>>> > >>>> Thanks > >>>> Naga > >>>> > >>>> ----- Original Message ----- > >>>> From: "Nagaprasad Sathyanarayana" <nsathyan@xxxxxxxxxx > ><mailto:nsathyan@xxxxxxxxxx>> > >>>> To: "Pranith Kumar Karampuri" <pkarampu@xxxxxxxxxx > ><mailto:pkarampu@xxxxxxxxxx>> > >>>> Cc: "Gluster Devel" <gluster-devel@xxxxxxxxxxx > ><mailto:gluster-devel@xxxxxxxxxxx>> > >>>> Sent: Saturday, May 30, 2015 7:23:21 AM > >>>> Subject: Re: gluster builds are failing in rpmbuilding > >>>> > >>>> Could it be due to the compilation errors? > >>>> > >>>> http://build.gluster.org/job/glusterfs-devrpms-el6/9019/ : > >>>> glusterd-locks.c:24:28: error: glusterd-errno.h: No such file or > >directory > >>>> CC glusterd_la-glusterd-mgmt-handler.lo > >>>> glusterd-locks.c: In function 'glusterd_mgmt_v3_lock': > >>>> glusterd-locks.c:557: error: 'EANOTRANS' undeclared (first use in this > >function) > >>>> glusterd-locks.c:557: error: (Each undeclared identifier is reported > >only once > >>>> glusterd-locks.c:557: error: for each function it appears in.) > >>>> make[5]: *** [glusterd_la-glusterd-locks.lo] Error 1 > >>>> make[5]: *** Waiting for unfinished jobs.... > >>>> make[4]: *** [all-recursive] Error 1 > >>>> make[3]: *** [all-recursive] Error 1 > >>>> make[2]: *** [all-recursive] Error 1 > >>>> make[1]: *** [all-recursive] Error 1 > >>>> make: *** [all] Error 2 > >>>> RPM build errors: > >>>> error: Bad exit status from /var/tmp/rpm-tmp.E46NjW (%build) > >>>> Bad exit status from /var/tmp/rpm-tmp.E46NjW (%build) > >>>> Child return code was: 1 > >>>> > >>>> http://build.gluster.org/job/glusterfs-devrpms/9141/ : > >>>> glusterd-locks.c:24:28: fatal error: glusterd-errno.h: No such file or > >directory > >>>> #include "glusterd-errno.h" > >>>> ^ > >>>> compilation terminated. > >>>> CC glusterd_la-glusterd-mgmt-handler.lo > >>>> CC glusterd_la-glusterd-mgmt.lo > >>>> make[5]: *** [glusterd_la-glusterd-locks.lo] Error 1 > >>>> > >>>> http://build.gluster.org/job/glusterfs-devrpms-el7/2179/ : > >>>> glusterd-locks.c:24:28: fatal error: glusterd-errno.h: No such file or > >directory > >>>> #include "glusterd-errno.h" > >>>> ^ > >>>> compilation terminated. > >>>> CC glusterd_la-glusterd-mgmt.lo > >>>> make[5]: *** [glusterd_la-glusterd-locks.lo] Error 1 > >>>> make[5]: *** Waiting for unfinished jobs.... > >>>> glusterd-mgmt.c:26:28: fatal error: glusterd-errno.h: No such file or > >directory > >>>> #include "glusterd-errno.h" > >>>> ^ > >>>> compilation terminated. > >>>> > >>>> > >>>> Thanks > >>>> Naga > >>>> > >>>> ----- Original Message ----- > >>>> From: "Pranith Kumar Karampuri" <pkarampu@xxxxxxxxxx > ><mailto:pkarampu@xxxxxxxxxx>> > >>>> To: "Gluster Devel" <gluster-devel@xxxxxxxxxxx > ><mailto:gluster-devel@xxxxxxxxxxx>> > >>>> Sent: Saturday, May 30, 2015 6:57:41 AM > >>>> Subject: gluster builds are failing in rpmbuilding > >>>> > >>>> hi, > >>>> I don't understand rpmbuild logs that well. But the following > >seems > >>>> to be the issue: > >>>> Start: build phase for glusterfs-3.8dev-0.314.git471b2e0.el6.src.rpm > >>>> Start: build setup for glusterfs-3.8dev-0.314.git471b2e0.el6.src.rpm > >>>> Finish: build setup for glusterfs-3.8dev-0.314.git471b2e0.el6.src.rpm > >>>> Start: rpmbuild glusterfs-3.8dev-0.314.git471b2e0.el6.src.rpm > >>>> ERROR: Exception(glusterfs-3.8dev-0.314.git471b2e0.el6.src.rpm) > >>>> Config(epel-6-x86_64) 1 minutes 5 seconds > >>>> > >>>> Please feel free to take a look at the following links for sample > >runs: > >>>> http://build.gluster.org/job/glusterfs-devrpms-el6/9019/console > >>>> http://build.gluster.org/job/glusterfs-devrpms/9141/console > >>>> http://build.gluster.org/job/glusterfs-devrpms-el7/2179/console > >>>> > >>>> Pranith > >>>> _______________________________________________ > >>>> Gluster-devel mailing list > >>>> Gluster-devel@xxxxxxxxxxx <mailto:Gluster-devel@xxxxxxxxxxx> > >>>> http://www.gluster.org/mailman/listinfo/gluster-devel > >>>> > >>>> _______________________________________________ > >>>> Gluster-devel mailing list > >>>> Gluster-devel@xxxxxxxxxxx <mailto:Gluster-devel@xxxxxxxxxxx> > >>>> http://www.gluster.org/mailman/listinfo/gluster-devel > >>> > >>> > >>> _______________________________________________ > >>> Gluster-devel mailing list > >>> Gluster-devel@xxxxxxxxxxx <mailto:Gluster-devel@xxxxxxxxxxx> > >>> http://www.gluster.org/mailman/listinfo/gluster-devel > >> > >> > >> _______________________________________________ > >> Gluster-devel mailing list > >> Gluster-devel@xxxxxxxxxxx <mailto:Gluster-devel@xxxxxxxxxxx> > >> http://www.gluster.org/mailman/listinfo/gluster-devel > > > > _______________________________________________ > Gluster-devel mailing list > Gluster-devel@xxxxxxxxxxx > http://www.gluster.org/mailman/listinfo/gluster-devel _______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-devel
