We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Example build: https://copr.fedorainfracloud.org/coprs/g/copr/PyPI/build/7141457/
When the source build fails, the button still offers links to the RPM build roots that did not even start (so there are no logs).
The text was updated successfully, but these errors were encountered:
There is:
{% for chroot in chroots %} <li><a href="{{ url |format(build.id, chroot.name) }}">Report {{ chroot.name }}</a></li> {% else %} <li><a href="{{ url |format(build.id, 'srpm-builds') }}">Report SRPM build</a></li> {% endfor %}
So this won't probably happen for all SRPM but only for builds that specified their chroots in advance and failed on SRPM.
Sorry, something went wrong.
nikromen
Successfully merging a pull request may close this issue.
Example build: https://copr.fedorainfracloud.org/coprs/g/copr/PyPI/build/7141457/
When the source build fails, the button still offers links to the RPM build roots that did not even start (so there are no logs).
The text was updated successfully, but these errors were encountered: