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!
Dne 1.6.2016 v 02:25 David Haltinner napsal(a):
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?
Our backend was stuck this night and morning. It should be ok now.
copr-devel@lists.stg.fedorahosted.org