On Wed, 11 Jan 2017 12:39:12 +0100 Kai Engert <k...@kuix.de> wrote: > On Wed, 2017-01-11 at 12:16 +0100, Pavel Raiskup wrote: > > > The relevant task is: > > > > > > https://koji.fedoraproject.org/koji/taskinfo?taskID=17230493 > > > > > > Thank you, > > > > Could the build go OOM? > > mock_output.log doesn't report anything after rpmbuild is started, it > seems the task gets interrupted. > > build.log shows the build completes, and the test suite execution has > started, which takes a rather long time, with many individual tests, > which includes starting and termination of background processes. That > log also stops reporting progress somewhere in the middle of the > expected tests. > > Exhausted resources (like OOM) seems like a plausible explanation for > the unexpected interruption of the task. > > Could someone with administrator access on the arm builder machine > please check if that theory is correct? Are there known limitations?
Yes, it seems that is the case: [Tue Jan 10 10:13:13 2017] Out of memory: Kill process 22877 (kojid) score 4 or sacrifice child [Tue Jan 10 10:13:13 2017] Killed process 23210 (mock) total-vm:28592kB, anon-rss:8060kB, file-rss:10016kB, shmem-rss:0k B kevin
pgp2pTpXEHTa0.pgp
Description: OpenPGP digital signature
_______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
