Basically, there is a difference in build-time calculation for chroots and builds. For chroot, it is end_time - start_time and for build it is chroot_max_end_time - chroot_min_end_time (in other words, for a build, all its chroots are considered in time calculation).

The thing is that your x86_64 build got stuck and was restarted after 48 hours at which point chroot's start_time got reset. You can find out where it got stuck from the logs prev_build_backup subdirectory in the build's results directory.

It's quite common that kernel (or long-running) builds get restarted. I am not sure why exactly it happens and if we should take a look at it. Let us know if the problems are reoccurring.

clime

On Mon, Oct 24, 2016 at 3:28 PM, Michael J Gruber < michaeljgruber+fedoraproject@gmail.com> wrote:

Hi there,

in https://copr.fedorainfracloud.org/coprs/mjg/kernel-hp6715b/builds/, I have an x86_64 build with some strange stats:

467858 kernel 4.7.9-200.hp6715b.fc24 3 days ago 9 hours running

Build time goes up for a few hours and then apparentyl gets reset on that page, but keeps growing on the build's page https://copr.fedorainfracloud. org/coprs/mjg/kernel-hp6715b/build/467858/.

The corresponding i386 finished in due time.

Should I somehow cancel and resubmit that build to get it unstuck? I never had that with (almost) the same spec before, it's fedora's kernel spec plus 1 more patch. _______________________________________________ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-leave@lists.fedorahosted.org