copr-devel June 2016

copr-devel@lists.fedorahosted.org

10 participants
6 discussions

copr-dist-git webui is working again
by Miroslav Suchý 30 Jun '16

30 Jun '16

Recently I've got reports that http://copr-dist-git.fedorainfracloud.org/cgit/ was timeouting. I enabled cgit cache and disabled access for robots and it seems it helped. If you encounter some problems please report. Mirek

1 0

copr waiting task queue
by Clinton Work 26 Jun '16

26 Jun '16

The following chromium job has been running for the past 2 days and it looks like it is backing up the rest of the build queues. There are now 168 build jobs waiting in the queue. Running Project Build Package Name Package Version Chroot 2 days lantw44/chromium 362159 chromium 51.0.2704.106-1.fc23 fedora-23-x86_64 -- Clinton Work Airdrie, AB

2 1

New release of Copr
by Miroslav Suchý 20 Jun '16

20 Jun '16

Hi, I just upgraded Copr instance to new version. There is one big change. You can now lower priority of your build. It was introduced to easy rebuild of rubygems and pypi. But it can be used by CI systems later. Copr-cli from our git, has --background option already. It lowers the priority. But due compatibility reason we will not push the package into main Fedora and we will wait one or two weeks. If you want to give it try, then you can install it from our copr project. Mirek

5 5

Unable to login to COPR
by Zygmunt Krynicki 14 Jun '16

14 Jun '16

Hey. I can access my FAS account (as you can see) but each attempt to log into copr at https://copr.fedorainfracloud.org/ or http://copr-fe-dev.cloud.fedoraproject.org/ results in timeouts in the browser. I'm using Firefox 47 on Fedora 24. Is there any issue with the infrastructure or is it possible that there is something wrong on my end? Best regards ZK

3 2

70k+ tasks sent to Copr
by Miroslav Suchý 11 Jun '16

11 Jun '16

I am just sending more than 70 000 tasks to production instance of Copr. Why? Because of: http://miroslav.suchy.cz/blog/archives/2016/04/21/wip_rebuilding_all_pypi_m… I'm throttling the speed and I am sending one task each 15 seconds. So it will take 12 days before I sent everything. On the other hand there should be no long queue. If you will see some long queue in "Waiting" despite my throttling, then I would like to emphasise that every user (including me) can have only 6 concurent tasks. And we can have up to 25 builders in parallel. So there is still 19 builders always available to process task of other users, so your task should be build as fast as usually. Of course there can be some bug. So if you think that something bad happened then please contact me. -- Miroslav Suchy, RHCA Red Hat, Senior Software Engineer, #brno, #devexp, #fedora-buildsys

3 3

new 24hr timeout
by David Haltinner 01 Jun '16

01 Jun '16

I'm wondering if the 24 hr timeout change is too long. I tossed a bunch of builds in, and it decided to stall out with no log messages on four of them, filling the build machines up so others builds are stuck waiting now. These were three 10 minute builds and one two hour build on a normal decent quad core VM. Perhaps 24 hrs is too long to timeout? Or limit the number of build machines one user can utilize at a time? Just a thought. Thanks!

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

copr-devel June 2016