On Fri, 5 Aug 2016 10:30:38 +0200
Florian Weimer <fweimer(a)redhat.com> wrote:
On 08/04/2016 05:07 PM, Peter Robinson wrote:
> All the details of the proposal along with FAQ have been put on a
> wiki page here[1]
> so please go and read it and ask any questions that aren't answered
> in the FAQ here.
For rawhide, ppc.koji is currently behind primary by two weeks (or
even more). What's the cause of these delays? Is it koji-shadow
bugs or lack of automation? I hope it's not raw builder throughput.
nothing in the infrastructure, the problem is with ruby and mariadb
build that are failing in their test-suites and we are unable to
reproduce them outside of koji. And with Flock this week there was
little to no progress on the issue. koji-shadow builds the builds in the
correct order (with same buildroots as were used in primary) it means a
missing (broken) build stops the whole process.
ruby =
https://bugzilla.redhat.com/show_bug.cgi?id=1361037
mariadb is about resource exhaustion when starting threads (IIRC),
interestingly recent golang build in primary koji sees very similar
issue
I know that there are koji-shadow bugs which cause build root
corruption, and the NVR sync from primary is not exact (in the sense
koji-shadow itself shouldn't cause buildroot corruption, rather wrong
configuration change
that packages are built against different libraries), so I hope we
can get rid of koji-shadow.
and there are other reasons to get rid of koji-shadow too :-)
Dan