Hello Barry, thank you for the feedback. > Maybe make "See logs for more details." link logs to the chroot?
That could work when the build is submitted to only one chroot. But usually, a build is submitted into many chroots, and if more of them fail, what would we link then? The results table, where chroot names are, contains also a Logs column with links to logs for each of the chroots. So maybe just rewording the "Build failed. See logs for more details." to say something like "Build failed. For more information see logs in the results section"? Jakub On Fri, Aug 26, 2022 at 5:26 PM Barry Scott <[email protected]> wrote: > > I'm looking at this page: > > https://copr.fedorainfracloud.org/coprs/barryascott/python-qt6/build/4769202/ > > Status: failed - Build failed. See logs for more details. > > I do not see an obvious link to the "logs" that it is telling to me view. > > After enough clicking I figured out that its in the chroot that I need to > look. > > Maybe make "See logs for more details." link logs to the chroot? > > Barry > _______________________________________________ > copr-devel mailing list -- [email protected] > To unsubscribe send an email to [email protected] > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedorahosted.org/archives/list/[email protected] > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue _______________________________________________ copr-devel mailing list -- [email protected] To unsubscribe send an email to [email protected] Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/[email protected] Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
