On Mon, Feb 4, 2019 at 5:14 AM Kevin Fenzi <kevin@xxxxxxxxx> wrote: > > On 1/31/19 4:52 PM, Neal Gompa wrote: > > ...snip... > > > COPR was supposed to be that outlet, but no one gives a damn about it. > > Everyone complains that the service is "bad" and that the design is > > "bad" but no one wants to actually constructively improve it. The > > quality of service on COPR has fallen due to lack of care and > > unwillingness to invest, so what are we supposed to do? The horrible > > I've heard you and some others say this, but can you perhaps expand on > it? How has quality of service of copr fallen? > > There are times when a bunch of builds are dumped on it that it takes a > bit to catch up, but it's usually like an hour not days or anything. > Is it the build time you refer to? Or something(s) else? > Aside from the times when it falls over for various reasons, I've had entire days where I wait for a build to even start, because people who use it for doing things like building KDE, chromium, or the Linux kernel occupy literally all the available builder slots for a long time. There aren't that many slots and it's easy to fill that up. There's usually a large queue of packages to build, but not enough builders to allow them to get done. That indicates two things: 1. The builders are weak and so builds take a long time (which means slots are held up longer) 2. The demand and popularity of the service isn't being handled appropriately (i.e. it should get more builders provisioned). I don't do things like build kernels often, but when I do, it usually doesn't take all day. But stuff like Chromium is hard to build locally, so I appreciate that we have somewhere to build and publish. But, as of right now, there are 16 tasks running, with 85 tasks waiting for a builder. I wish we had visualizations like the ones OBS has[1][2], so that we have an idea of how stuff is occupied and know at a glance that we're over capacity. All I know right now is that it's easy to see that COPR gets into a state where I just wind up waiting for builds to even start. [1]: https://build.opensuse.org/monitor [2]: https://build.opensuse.org/monitor/old -- 真実はいつも一つ！/ Always, there's only one truth! _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
