copr-devel April 2019

copr-devel@lists.fedorahosted.org

7 participants
9 discussions

Determine root.log vs build.log failures
by Miro Hrončok 25 Jun '19

25 Jun '19

Hey! Koji is always very nice and it tells me whether a build failure was caused by root.log or build.log. See for example: https://koji.fedoraproject.org/koji/taskinfo?taskID=28963878 BuildError: error building package (arch x86_64), mock exited with status 1; see build.log for more information Is Copr presenting this kind of information somewhere? (I need to fetch it for hundreds of builds.) I could probably HTTP HEAD the build.log and check Content-Length to guess a root.log failure, but it feels weird... Thanks for tips. -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok

3 3

Attempt to build SRPM have failed:
by Miro Hrončok 29 Apr '19

29 Apr '19

I have plenty of SRPm errors like this: Building for target x86_64 Wrote: /builddir/build/SRPMS/python-doit-0.31.1-5.fc31.src.rpm Finish: rpmbuild -bs INFO: chroot_scan: 3 files copied to /var/lib/copr-rpmbuild/results/chroot_scan INFO: /var/lib/mock/895102-fedora-rawhide-x86_64-1556487528.374044/root/var/log/dnf.rpm.log /var/lib/mock/895102-fedora-rawhide-x86_64-1556487528.374044/root/var/log/dnf.librepo.log /var/lib/mock/895102-fedora-rawhide-x86_64-1556487528.374044/root/var/log/dnf.log Finish: buildsrpm ERROR: Exception(/tmp/tmp8__qgt_0/python-doit.spec) Config(895102-fedora-rawhide-x86_64) 1 minutes 8 seconds INFO: Results and/or logs in: /var/lib/copr-rpmbuild/results INFO: Cleaning up build root ('cleanup_on_failure=True') Start: clean chroot INFO: unmounting tmpfs. Finish: clean chroot Traceback (most recent call last): File "/usr/libexec/mock/mock", line 977, in <module> main() File "/usr/lib/python3.6/site-packages/mockbuild/trace_decorator.py", line 96, in trace result = func(*args, **kw) File "/usr/libexec/mock/mock", line 766, in main run_command(options, args, config_opts, commands, buildroot, state) File "/usr/lib/python3.6/site-packages/mockbuild/trace_decorator.py", line 96, in trace result = func(*args, **kw) File "/usr/libexec/mock/mock", line 864, in run_command do_buildsrpm(config_opts, commands, buildroot, options, args) File "/usr/lib/python3.6/site-packages/mockbuild/trace_decorator.py", line 96, in trace result = func(*args, **kw) File "/usr/libexec/mock/mock", line 559, in do_buildsrpm cmd=cmd, post=None, clean=clean) File "/usr/lib/python3.6/site-packages/mockbuild/trace_decorator.py" (the exception itself is probably missing from the log.) What can it be? See https://copr.fedorainfracloud.org/coprs/g/python/python3.8/builds/ failed builds without package name. -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok

2 1

Re: Legal flag raised on rpm-gitoverlay-1556488700.270103
by Miroslav Suchý 29 Apr '19

29 Apr '19

Dne 29. 04. 19 v 0:39 root(a)copr-fe.cloud.fedoraproject.org napsal(a): > rpmsoftwaremanagement generates dozens of empty projects. > It doesn't seem normal, more like some bot goes crazy. > Contact on owner is: rpmsoftwaremanagement <rpmsoftwaremanagement(a)gmail.com> > Reported by zawertun <zawertun(a)gmail.com> > It is fine. They are creating new project for every pull request and as far I can see, they really build something into those projects. I spoke to them some time ago and I asked them to tick the "Hide from front page". They promised to do, but it will need some time. Miroslav

1 0

Resubmit via CLI or Python API
by Miro Hrončok 28 Apr '19

28 Apr '19

Hey again. I like to resubmit a failed build via command line. I didn't find this option in copr --help or in https://python-copr.readthedocs.io I'd like to avoid reuploading the SRPM. In the web frontend, I just navigate to a failed build, click Resubmit - "Resubmitting a build will rebuild the same sources again." -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok

2 2

New Copr release
by Jakub Kadlcik 25 Apr '19

25 Apr '19

Hello, I am happy to announce a new Copr release. This time we have focused mainly on improving a CI experience and freeing up some disk space, but there is much more. These are some highlights from this release. - CLI support for managing permissions ------------------------------------ For quite some time, you have asked for a possibility to manage project permissions through copr-cli or API. This is now possible, see copr-cli request-permissions --help copr-cli list-permissions --help copr-cli edit-permissions --help - Temporary projects ------------------ Many people use Copr for CI, which may include creating new projects. Those are usually relevant for only a limited time and after that just floods up the projects list. Instead of automatizing the deletion of old projects all by yourself, try using temporary projects. When creating or editing a project, it is possible to set an optional "Delete after days" field in the Settings tab. There is also a command line option for this. copr-cli create ... --delete-after-days <number> copr-cli modify ... --delete-after-days <number> - Automatic removal of old builds ------------------------------- Another feature useful for CI, but also for normal projects. Sometimes, you don't care about old builds and they just slow working with builds table. Avoid this by going to package settings and specifying the optional "Max number of builds" parameter. Alternatively, use a command line. copr-cli add-package-* --max-builds <number> copr-cli edit-package-* --max-builds <number> This keeps last <number> builds of this package. Older builds are automatically deleted. Note that our general policy for [builds retention](https://docs.pagure.org/copr.copr/user_documentation.html#how-lo… still applies. - Pagure CI fixes ---------------- Copr is for quite some time listening on fedmsg to react on PR and PUSH events from Pagure (both src.fedoraproject.org and pagure.io). However, previously it had several limitations; 1) only the last commit from "push" or pull-request was analyzed, and thus only builds for packages updated by _the last_ commit were triggered, this is now fixed and copr analyses complete push/pull-request changes, 2) only one build per pull-reqeust could ever exist, this artificial rule was relaxed and now each PR update (new commit, rebase, ...) triggers a new copr build, 3) the fedmsg listener stopped receiving messages after some time and a restart was needed, workaround for this was installed (and we plan to move to fedora-messaging which should be more reliable), 4) there was a small rhbz#1699245 bug. As a bonus point, it is now enough to add a pull-request comment with `[copr-build]` keyword to manually (re)trigger the CI builds. - Saving up some disk space ------------------------- We are struggling with low disk space and hoping to free some up by removing backend and distgit data for old builds. To be specific - we are now removing: * old SRPM import logs * old tar files from dist-git look-aside cache * SRPM from failed builds older than 14 days - Turning off notifications for outdated chroots removal ------------------------------------------------------ Talking of disk space, we have recently started sending notifications about an upcoming deletion of builds for outdated chroots. The notifications suggest that if you still care about an outdated distribution, going to project settings and prolong the time for which the data is going to be preserved. If you don't care about it and don't want to be bothered by emails, you can now instantly expire the time and schedule the chroot to be removed. - Respecting module buildorder ---------------------------- When building a module, the `buildorder` was not respected. This issue is now fixed. - Private data in separate tables ------------------------------- We have moved secret/private data about users and projects to separate tables. This alone is not very interesting information. However, it will allow us to dump our database (except for those private tables of course) and share them to the public. This will allow you to do custom data analysis and statistics. Jakub

1 0

Outage: Upgrade of Copr servers - 2019-04-24 17:00 UTC
by Jakub Kadlcik 23 Apr '19

23 Apr '19

There will be an outage starting at 2019-04-24 17:00 UTC, which will last approximately 4 hours. To convert UTC to your local time, take a look at https://fedoraproject.org/wiki/UTCHowto or run: date -d '2019-04-24 17:00 UTC' Reason for outage: Upgrade of Copr services to the newest version. Affected Services: copr-frontend - https://copr.fedorainfracloud.org copr-backend - https://copr-be.cloud.fedoraproject.org/ copr-distgit copr-keygen Ticket Link: https://pagure.io/fedora-infrastructure/issue/7731 Contact Information: Please join #fedora-admin in irc.freenode.net or add comments to the ticket for this outage above.

1 0

IOError: Failed to write to /tmp/numpy_test_big_arrays....npy: [Errno 28] No space left on device
by Miro Hrončok 11 Apr '19

11 Apr '19

I just got this error in Copr. Should I skip big_arrays tests, or is this some quota on /tmp that can be enlarged? Thanks. -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok

2 1

Forked project
by Antonio Trande 10 Apr '19

10 Apr '19

Hi all. This [1] is a forked project of python3.8 [2]; inside there are all forked packages previously built but, if i require a new build for testing Python 3.8, are not used the packages from the project [3] (i see Python 3.7.3 as dependency). What am I doing wrong? [1] https://copr.fedorainfracloud.org/coprs/sagitter/python3.8/ [2] https://copr.fedorainfracloud.org/coprs/g/python/python3.8/ [3] https://copr-be.cloud.fedoraproject.org/results/sagitter/python3.8/fedora-r… Regards. -- --- Antonio Trande Fedora Project mailto 'sagitter at fedoraproject dot org' GPG key: 0x6e0331dd1699e4d7 GPG key server: https://keys.fedoraproject.org/

4 4

Build is pending but not listed in pending queue
by Miro Hrončok 03 Apr '19

03 Apr '19

Hi. My build has been pending for hours: https://copr.fedorainfracloud.org/coprs/g/python/python3.8/build/876568/ But it is not listed in https://copr.fedorainfracloud.org/status/pending/ I've tried to add another build, it is again pending and again not listed. Is something broken? Thanks. -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok

2 3

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

copr-devel April 2019