Hi Team,
I have been trying to run the following command to fix the centos ci nightly builds but Its failing I am not sure what's wrong here.
Any help would be appreciated.
# /usr/bin/mock --root epel-8-x86_64 --with=gnfs --resultdir /srv/gluster/nightly/master/8/x86_64 --rebuild /root/centosci/glusterfs/glusterfs-20201007.d1d7a6f-0.0.autobuild.src.rpm
.
.
.
RPM build errors:
error: Directory not found: /builddir/build/BUILDROOT/glusterfs-20201007.d1d7a6f-0.0.el8.x86_64/gluster
error: File not found: /builddir/build/BUILDROOT/glusterfs-20201007.d1d7a6f-0.0.el8.x86_64/gluster/__init__.*
error: File not found: /builddir/build/BUILDROOT/glusterfs-20201007.d1d7a6f-0.0.el8.x86_64/gluster/__pycache__
error: File not found: /builddir/build/BUILDROOT/glusterfs-20201007.d1d7a6f-0.0.el8.x86_64/gluster/cliutils
Directory not found: /builddir/build/BUILDROOT/glusterfs-20201007.d1d7a6f-0.0.el8.x86_64/gluster
File not found: /builddir/build/BUILDROOT/glusterfs-20201007.d1d7a6f-0.0.el8.x86_64/gluster/__init__.*
File not found: /builddir/build/BUILDROOT/glusterfs-20201007.d1d7a6f-0.0.el8.x86_64/gluster/__pycache__
File not found: /builddir/build/BUILDROOT/glusterfs-20201007.d1d7a6f-0.0.el8.x86_64/gluster/cliutils
Finish: rpmbuild glusterfs-20201007.d1d7a6f-0.0.autobuild.src.rpm
Finish: build phase for glusterfs-20201007.d1d7a6f-0.0.autobuild.src.rpm
ERROR: Exception(/root/centosci/glusterfs/glusterfs-20201007.d1d7a6f-0.0.autobuild.src.rpm) Config(epel-8-x86_64) 6 minutes 19 seconds
INFO: Results and/or logs in: /srv/gluster/nightly/master/8/x86_64
INFO: Cleaning up build root ('cleanup_on_failure=True')
Start: clean chroot
Finish: clean chroot
ERROR: Command failed:
# /usr/bin/systemd-nspawn -q -M e76a1e2f68cc4c88af4159fea2987ad1 -D /var/lib/mock/epel-8-x86_64/root -a -u mockbuild --capability=cap_ipc_lock --bind=/tmp/mock-resolv.kxdftj8r:/etc/resolv.conf --bind=/dev/loop-control --bind=/dev/loop0 --bind=/dev/loop1 --bind=/dev/loop2 --bind=/dev/loop3 --bind=/dev/loop4 --bind=/dev/loop5 --bind=/dev/loop6 --bind=/dev/loop7 --bind=/dev/loop8 --bind=/dev/loop9 --bind=/dev/loop10 --bind=/dev/loop11 --setenv=TERM=vt100 --setenv=SHELL=/bin/bash --setenv=HOME=/builddir --setenv=HOSTNAME=mock --setenv=PATH=/usr/bin:/bin:/usr/sbin:/sbin --setenv=PROMPT_COMMAND=printf "\033]0;<mock-chroot>\007" --setenv=PS1=<mock-chroot> \s-\v\$ --setenv=LANG=C.UTF-8 --resolv-conf=off bash --login -c /usr/bin/rpmbuild -bb --target x86_64 --nodeps /builddir/build/SPECS/glusterfs.spec
.
.
.
RPM build errors:
error: Directory not found: /builddir/build/BUILDROOT/glusterfs-20201007.d1d7a6f-0.0.el8.x86_64/gluster
error: File not found: /builddir/build/BUILDROOT/glusterfs-20201007.d1d7a6f-0.0.el8.x86_64/gluster/__init__.*
error: File not found: /builddir/build/BUILDROOT/glusterfs-20201007.d1d7a6f-0.0.el8.x86_64/gluster/__pycache__
error: File not found: /builddir/build/BUILDROOT/glusterfs-20201007.d1d7a6f-0.0.el8.x86_64/gluster/cliutils
Directory not found: /builddir/build/BUILDROOT/glusterfs-20201007.d1d7a6f-0.0.el8.x86_64/gluster
File not found: /builddir/build/BUILDROOT/glusterfs-20201007.d1d7a6f-0.0.el8.x86_64/gluster/__init__.*
File not found: /builddir/build/BUILDROOT/glusterfs-20201007.d1d7a6f-0.0.el8.x86_64/gluster/__pycache__
File not found: /builddir/build/BUILDROOT/glusterfs-20201007.d1d7a6f-0.0.el8.x86_64/gluster/cliutils
Finish: rpmbuild glusterfs-20201007.d1d7a6f-0.0.autobuild.src.rpm
Finish: build phase for glusterfs-20201007.d1d7a6f-0.0.autobuild.src.rpm
ERROR: Exception(/root/centosci/glusterfs/glusterfs-20201007.d1d7a6f-0.0.autobuild.src.rpm) Config(epel-8-x86_64) 6 minutes 19 seconds
INFO: Results and/or logs in: /srv/gluster/nightly/master/8/x86_64
INFO: Cleaning up build root ('cleanup_on_failure=True')
Start: clean chroot
Finish: clean chroot
ERROR: Command failed:
# /usr/bin/systemd-nspawn -q -M e76a1e2f68cc4c88af4159fea2987ad1 -D /var/lib/mock/epel-8-x86_64/root -a -u mockbuild --capability=cap_ipc_lock --bind=/tmp/mock-resolv.kxdftj8r:/etc/resolv.conf --bind=/dev/loop-control --bind=/dev/loop0 --bind=/dev/loop1 --bind=/dev/loop2 --bind=/dev/loop3 --bind=/dev/loop4 --bind=/dev/loop5 --bind=/dev/loop6 --bind=/dev/loop7 --bind=/dev/loop8 --bind=/dev/loop9 --bind=/dev/loop10 --bind=/dev/loop11 --setenv=TERM=vt100 --setenv=SHELL=/bin/bash --setenv=HOME=/builddir --setenv=HOSTNAME=mock --setenv=PATH=/usr/bin:/bin:/usr/sbin:/sbin --setenv=PROMPT_COMMAND=printf "\033]0;<mock-chroot>\007" --setenv=PS1=<mock-chroot> \s-\v\$ --setenv=LANG=C.UTF-8 --resolv-conf=off bash --login -c /usr/bin/rpmbuild -bb --target x86_64 --nodeps /builddir/build/SPECS/glusterfs.spec
Regards
Rinku
On Fri, Oct 9, 2020 at 12:22 PM Niels de Vos <ndevos@xxxxxxxxxx> wrote:
On Thu, Oct 08, 2020 at 04:21:50PM +0530, Rinku Kothiya wrote:
> Hi Niels,
>
> Yaniv wanted the glusterfs nightly builds generated to be tested for
> performance bottlenecks.
>
> I was working on the below project :
> https://github.com/gluster/gluster-performance-test-suite
>
> As of now we are running the above script on the glusterfs-nightly builds
> every night through a jenkins machine.
> Currently we have only been using Glusterfs-EL7 Nightly builds. But for
> testing the Gusfterfs-EL8 nightly build, I need those nightly builds to be
> generated.
> I raised a request with Deepshikha and she said that you have been looking
> at it in the past.
Please have a look at the Jenkins Jobs Builder scripts from
https://github.com/gluster/centosci/ that are used to run these jobs.
For the nightly GlusterFS builds, there are two jobs involved:
1. jobs/build-rpms.yml contains the different versions and architectures
that the gluster_build-rpms job can build. It needs to be extended to
support the `release-8` branch
2. jobs/nightly-rpm-builds.yml does the triggering of the 1st job. It
passes parameters to the job, which then will do the builds. Som in
order to add a build for GlusterFS-8, inlucde an new `trigger-build`
section.
3. jobs/scripts/nightly-builds/nightly-builds.sh is the script that does
the actual work. You should be able to execute it manually on a
CentOS system (set the environment like the parameters from 2) and
see if it works for GlusterFS-8. Ideally the script does not need any
changes.
You can send a PR with changes that you need, and once it is merged (by
Deepshika or one of the other active maintainers), it should
automatically get updated in the Jenkins environment, and the next day
there should be a new "Gluster 8 Nightly" repository.
Adding gluster-devel to CC, as this information should enable others to
add or improve CI jobs too.
Good luck!
Niels
_______________________________________________ Community Meeting Calendar: Schedule - Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC Bridge: https://bluejeans.com/441850968 Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx https://lists.gluster.org/mailman/listinfo/gluster-devel
