| Summary: | A single failure makes the whole monitoring line red | ||
|---|---|---|---|
| Product: | [Community] Copr | Reporter: | Fabio Alessandro Locati <fale> |
| Component: | frontend | Assignee: | Jakub Kadlčík <jkadlcik> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | unspecified | CC: | clime, petersen, przemo, quantum.analyst |
| 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-03-29 12:20:45 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: | |
|
Description
Fabio Alessandro Locati
2016-02-10 09:09:33 UTC
This is rather annoying since all of my builds are now "pending" since the wait for ppc is usually quite long. It makes it difficult to find builds that actually failed but I never got around to re-submitting. *** Bug 1309603 has been marked as a duplicate of this bug. *** Hello guys, thank you for the feedback. > If a build fails on a single platform is marked as failed for every platform When we are talking about `build state` or `package state` that means only one value representing the whole build, expected behavior is to show the most pessimistic option. (i.e. if one chroot fails and all other chroots succeeds, the whole build is marked as failed). But of course when you see details of the build, every chroot should show it's proper state. If it doesn't work this way, please refer me on the page/build which is bugged. > Also, I've noticed that today (compared to a week ago) in the "Monitor" tab - > during building - all platforms are marked as building even if some of them > have already completed. I confirm a bug. Modified in: 9e53dd6 The report is about the Monitor page. Code with this fix is currently deployed on testing server. You can test it before it will be deployed to production. Please see: http://copr-fe-dev.cloud.fedoraproject.org (In reply to Jakub Kadlčík from comment #5) > Code with this fix is currently deployed on testing server. > You can test it before it will be deployed to production. > Please see: http://copr-fe-dev.cloud.fedoraproject.org On the dev version is working as expected :) Copr production machines were upgraded to version containing a fix to this issue. If you are not satisfied with provided solution, please feel free to reopen this. |