Mock Lab
The mock lab was flawless for both of the packages (which and less)
Here is the output of which
INFO: mock.py version 1.1.33 starting...
Start: init plugins
INFO: selinux enabled
Finish: init plugins
Start: run
INFO: Start(less-458-4.fc19.src.rpm) Config(fedora-19-x86_64)
Start: lock buildroot
Start: clean chroot
Finish: clean chroot
Finish: lock buildroot
Start: chroot init
Start: lock buildroot
Mock Version: 1.1.33
INFO: Mock Version: 1.1.33
INFO: calling preinit hooks
INFO: enabled root cache
INFO: enabled yum cache
Start: cleaning yum metadata
Finish: cleaning yum metadata
INFO: enabled ccache
Start: device setup
Finish: device setup
Start: yum update
Start: Outputting list of available packages
Finish: Outputting list of available packages
Finish: yum update
Start: creating cache
Finish: creating cache
Finish: lock buildroot
Finish: chroot init
INFO: Installed packages:
Start: build phase for less-458-4.fc19.src.rpm
Start: device setup
Finish: device setup
Start: build setup for less-458-4.fc19.src.rpm
Finish: build setup for less-458-4.fc19.src.rpm
Start: rpmbuild -bb less-458-4.fc19.src.rpm
Start: Outputting list of installed packages
Finish: Outputting list of installed packages
Finish: rpmbuild -bb less-458-4.fc19.src.rpm
Finish: build phase for less-458-4.fc19.src.rpm
INFO: Done(less-458-4.fc19.src.rpm) Config(fedora-19-x86_64) 5 minutes 8 seconds
INFO: Results and/or logs in: /var/lib/mock/fedora-19-x86_64/result
Finish: run
[ron@f19 SRPMS]$ cd ~/Downloads/
[ron@f19 Downloads]$ mock -r fedora-19-x86_64 which-2.20-1.fc19.src.rpm
INFO: mock.py version 1.1.33 starting...
Start: init plugins
INFO: selinux enabled
Finish: init plugins
Start: run
INFO: Start(which-2.20-1.fc19.src.rpm) Config(fedora-19-x86_64)
Start: lock buildroot
Start: clean chroot
INFO: chroot (/var/lib/mock/fedora-19-x86_64) unlocked and deleted
Finish: clean chroot
Finish: lock buildroot
Start: chroot init
Start: lock buildroot
Mock Version: 1.1.33
INFO: Mock Version: 1.1.33
INFO: calling preinit hooks
INFO: enabled root cache
Start: unpacking root cache
Finish: unpacking root cache
INFO: enabled yum cache
Start: cleaning yum metadata
Finish: cleaning yum metadata
INFO: enabled ccache
Start: device setup
Finish: device setup
Start: yum update
Start: Outputting list of available packages
Finish: Outputting list of available packages
Finish: yum update
Finish: lock buildroot
Finish: chroot init
INFO: Installed packages:
Start: build phase for which-2.20-1.fc19.src.rpm
Start: device setup
Finish: device setup
Start: build setup for which-2.20-1.fc19.src.rpm
Finish: build setup for which-2.20-1.fc19.src.rpm
Start: rpmbuild -bb which-2.20-1.fc19.src.rpm
Start: Outputting list of installed packages
Finish: Outputting list of installed packages
Finish: rpmbuild -bb which-2.20-1.fc19.src.rpm
Finish: build phase for which-2.20-1.fc19.src.rpm
INFO: Done(which-2.20-1.fc19.src.rpm) Config(fedora-19-x86_64) 0 minutes 33 seconds
INFO: Results and/or logs in: /var/lib/mock/fedora-19-x86_64/result
Finish: run
I was really glad I switched gimp for which … It would have been a terrible pain to build an RPM package of gimp and then run mock with all the dependencies that gimp requires and the dependencies of dependencies.
Mock did not take too long to finish, perhaps a little bit more than building the RPM package. I was expecting mock to finish successfully for both packages since I spent a lot of time looking working on the spec file of each one.
--------------------------------------
Koji Lab
For the koji lab first I yum install fedora-packager then
I cd to /usr/bin and run ./fedora-packager-setup.
It prompts me for my FAS account and then It asks for an export password.
Afterwards I add the certificate to chrome and enter the export password. I test that I can sign in with koji. Everything seems good to go.
Testing less with Koji
I begin with the following command:
time s390-koji build f19 --scratch less-458-4.fc19.src.rpm
this is what I get back:
Created task: 1217365
Task info: http://s390.koji.fedoraproject.org/koji/taskinfo?taskID=1217365
Watching tasks (this may be safely interrupted)...
1217365 build (f19, less-458-4.fc19.src.rpm): free
1217365 build (f19, less-458-4.fc19.src.rpm): free -> open (fedora2.s390.bos.redhat.com)
1217366 buildArch (less-458-4.fc19.src.rpm, s390): free
1217367 buildArch (less-458-4.fc19.src.rpm, s390x): open (fedora3.s390.bos.redhat.com)
1217366 buildArch (less-458-4.fc19.src.rpm, s390): free -> open (fedora1.s390.bos.redhat.com)
1217366 buildArch (less-458-4.fc19.src.rpm, s390): open (fedora1.s390.bos.redhat.com) -> closed
0 free 2 open 1 done 0 failed
1217367 buildArch (less-458-4.fc19.src.rpm, s390x): open (fedora3.s390.bos.redhat.com) -> closed
0 free 1 open 2 done 0 failed
1217365 build (f19, less-458-4.fc19.src.rpm): open (fedora2.s390.bos.redhat.com) -> closed
0 free 0 open 3 done 0 failed
1217365 build (f19, less-458-4.fc19.src.rpm) completed successfully
real 5m14.094s
user 0m2.188s
sys 0m0.287s
I ran the same source file a second time for f18
real 3m45.686s
user 0m1.957s
sys 0m0.256s
Then for ppc-koji in f18
real 3m49.745s
user 0m1.713s
sys 0m0.234s
ppc-koji in f19
0 free 2 open 1 done 0 failed
gaierror: [Errno -2] Name or service not known
real 3m28.543s
user 0m1.694s
sys 0m0.219s
I got an error or warning for PPC in f19 but since it said 0 failed I ignored it, Nor I have any idea why the powerpc could not recognize what was clearly recognized in all of the other platforms.
time koji build f18 --scratch less-458-4.fc19.src.rpm
The first time I ran koji I forgot to time, so this is the second time I ran koji for the same file
real 2m55.563s
user 0m1.427s
sys 0m0.207s
Now for f19
real 3m5.445s
user 0m1.327s
sys 0m0.227s
Testing which with Koji
koji for f19
real 2m48.838s
user 0m1.152s
sys 0m0.197s
koji for f18
real 2m10.631s
user 0m1.358s
sys 0m0.208s
s390-koji for f18
real 2m58.190s
user 0m1.323s
sys 0m0.146s
ppc-koji for f19
real 2m57.790s
user 0m1.738s
sys 0m0.231s
ppc-koji for f18
real 1m30.340s
user 0m0.935s
sys 0m0.127s
In general Koji took longer to build than mock and rpmbuild for the same packets. Of course we have to take into account that there might not be a free machine always which will increase the time. In my case there was always a free machine but the Seneca network caused the time to increase due to either lag or upload speed etc. Ignoring the network the process is almost as fast as from my computer.
Koji in general is very versatile tool to test if your package will build in several architectures. Given that most likely we have at home a 32 or 64 bit machine. Process is fairly simple and the build time is fast for the packages done.
No comments:
Post a Comment