Bug 1196826

Summary: RFE: A build is marked as failed even though one chroot is still running
Product: [Community] Copr Reporter: Ryan Lerch <rlerch>
Component: frontendAssignee: clime
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: clime, jberan, projects.rg
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-05-05 13:06:29 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
screenshot none

Description Ryan Lerch 2015-02-26 20:40:41 UTC 
If a chroot of a build fails, the entire build is marked as "failed" at the top of the build details page when there is still a chroot in the running state.

See attached screenshot for an example.

Even though the screenshot does not show a logged in version of the page, the controls at the top of the page list the buttons for a failed build (Delete, or Resubmit). So there is no option ot cancel the build anymore even though it is still techincally running.

The build should be in a "running" state until all the chroots are either skipped, failed or success.
Comment 1 Ryan Lerch 2015-02-26 20:41:06 UTC 
Created attachment 995764 [details]
screenshot
Comment 2 Raphael Groner 2015-06-07 09:56:15 UTC 
+1
Comment 3 Raphael Groner 2015-06-07 09:58:45 UTC 
Another option would be to add another column into the builds overview table, showing the number of still running chroot jobs.
Comment 4 clime 2016-03-21 16:32:03 UTC 
Fixed by b924147b (https://github.com/fedora-copr/copr/commit/b924147bde8a50696be95f7368ac7dbf02dd2cef). Thanks.
Comment 5 Miroslav Suchý 2016-05-05 13:06:29 UTC 
Package including this fix has been deployed on production instance of Copr.