Learn more about these different git repos.
Other Git URLs
Could anyone with access to the build boxes please use ps ax to find out which tests got stuck in gcc builds: https://koji.fedoraproject.org/koji/taskinfo?taskID=60965411 and https://koji.fedoraproject.org/koji/taskinfo?taskID=60974250 ? I'll try to add some tracking of stuck processes using pstree -p + periodic checking of what leaf processes during make check don't make progress and perhaps try to kill them after some time, but the above builds were already second attempts to build gcc over the weekend and got stuck both again and I'd prefer not to repeat the 12+ hrs builds again.
Thanks.
The first of those seems to be done now, and the second is just finishing up. ;(
`-rpmbuild,352874 -bb --target s390x --nodeps /builddir/build/SPECS/gcc.spec |-{rpmbuild},160605 |-{rpmbuild},160606 |-bzip2,160625 -cd `-bzip2,160626 -cd
But we can try and gather from another one when it gets in that state?
The first one got a stuck test killed by mboddu, thanks. The s390x one doesn't seem to be making progress for hours. Anyway, the first build was more important than second.
Fixed it by killing the go test process, but the go testsuite needs to be fixed as it happened twice already.
Metadata Update from @mohanboddu: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.