Yes that will work, but the Logs in the results section do not link
to the
build.log.gz that contains the errors from rpmbuild.
You are right that build.log.gz isn't linked there, but
builder-live.log.gz is. In the majority of cases, the relevant error
can be found there. I think it should be the case for your build as
well, I can see some ModuleNotFoundError: No module named 'ply'
traceback.
Jakub
On Thu, Sep 1, 2022 at 7:16 PM Barry Scott <barry(a)barrys-emacs.org> wrote:
>
>
>
> > On 30 Aug 2022, at 23:08, Jakub Kadlcik <jkadlcik(a)redhat.com> wrote:
> >
> > 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"?
>
Yes that will work, but the Logs in the results section do not link
to the
build.log.gz that contains the errors from rpmbuild.
>
> I guess its easy enough to also all build.log.gz to the results section.
>
> I would put build.log.gz as the first log in the list on the basis that its
> likely to be the one most people need to read. Or is that just my use case?
>
> Barry
>
>
>
> >
> > Jakub
> >
> > On Fri, Aug 26, 2022 at 5:26 PM Barry Scott <barry(a)barrys-emacs.org>
wrote:
> >>
> >> I'm looking at this page:
> >>
> >>
https://copr.fedorainfracloud.org/coprs/barryascott/python-qt6/build/4769...
> >>
> >> 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 -- copr-devel(a)lists.fedorahosted.org
> >> To unsubscribe send an email to copr-devel-leave(a)lists.fedorahosted.org
> >> 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/copr-devel@lists.fedorahoste...
> >> Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
> > _______________________________________________
> > copr-devel mailing list -- copr-devel(a)lists.fedorahosted.org
> > To unsubscribe send an email to copr-devel-leave(a)lists.fedorahosted.org
> > 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/copr-devel@lists.fedorahoste...
> > Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
> _______________________________________________
> copr-devel mailing list -- copr-devel(a)lists.fedorahosted.org
> To unsubscribe send an email to copr-devel-leave(a)lists.fedorahosted.org
> 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/copr-devel@lists.fedorahoste...
> Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue