Created attachment 892813 [details] Screenshot from Copr Description of problem: It happened to me a few times, that build on all archs have finished, logs and rpms were downloaded from builders, the Copr web is showing correct "Ended on" time, but the build remained in 'Running' state. Example is build 11629 in http://copr.fedoraproject.org/coprs/dvratil/kde-frameworks/, which is still shown as Running in the interface. Previously, with some other build, the build has turned to Failed after more than 24 hours (but maybe Copr was restarted over night). This obviously breaks any automation tools that are waiting for the build to finish :-) From mockchain.log: http://pub.progdan.cz/kf5/srpm/4.99.0/kf5-kcoreaddons-4.99.0-2.fc20.src.rpm starting logfile: None results dir: /var/tmp/mockremote-YZqWi/build/results/fedora-rawhide-x86_64 config dir: /var/tmp/mockremote-YZqWi/build/configs/fedora-rawhide-x86_64 Fetching http://pub.progdan.cz/kf5/srpm/4.99.0/kf5-kcoreaddons-4.99.0-2.fc20.src.rpm Start build: /tmp/tmpJHPPpV/kf5-kcoreaddons-4.99.0-2.fc20.src.rpm building kf5-kcoreaddons-4.99.0-2.fc20.src.rpm End build: /tmp/tmpJHPPpV/kf5-kcoreaddons-4.99.0-2.fc20.src.rpm Success building kf5-kcoreaddons-4.99.0-2.fc20.src.rpm Results out to: /var/tmp/mockremote-YZqWi/build/results/fedora-rawhide-x86_64 Pkgs built: 1 Packages successfully built in this order: /tmp/tmpJHPPpV/kf5-kcoreaddons-4.99.0-2.fc20.src.rpm
Hmm this may happen when underlying Open Stack VM crash (happen for various reason). I thought that we have in place check which rerun "Running" task if they are older then several hours. I will check that.
I also encountered this problem. It did not stop, and can not be canceled. URL: https://copr.fedoraproject.org/coprs/mosquito/myrepo-testing/build/52886/
My God, waited two hours, and finally completed. On my computer, the compiler takes only one minute.
Again, it was OpenStack issues during night. When all spawned VM went directly into Error state and Copr was trying spinning new and new VM. So technically this state was correst. It was starting, but never got beyond that point. Hopefully this will be resolved by new OpenStack installation. I'm going to close this bug as there is nothing we can do in Copr code. This is infrastructure and needs to be reported to Fedora Infra. Best method is #fedora-buildsys or #fedora-admin on Freenode.