Failed builds have .log and .log.gz versions of the log files. The mail from failed builds refers to the .gz versions, but you want build.log to see the failure. I think it's general, but a recent example is https://copr-be.cloud.fedoraproject.org/results/loveshack/livhpc/epel-7-aarch64/01044291-proot/
Can you post the mail contents here? Each finished (not only failed) build contains stub '*.log' and the full log '*.log.gz'. So you really want the '*.log.gz' link.
If you look at the logs from the failed build I referenced, you'll see that the information about why it failed is in build.log, not build.log.gz. I think that's what's wrong.
We don't send emails, that's why I was asking you to provide mail contents. To judge who should I contact about the issue I needed to see the contents of the email (perhaps). But I was rather curious, I don't think we should do anything about this because new copr code should already redirect you from builder-live.log to builder-live.log.gz: https://pagure.io/copr/copr/issue/921
Ah, you mean build.log, not builder-live.log. Sorry. Nevermind, we don't send those emails. Please flip this bug against correct component, or provide the needed info.
I don't see any such redirect, and I don't see why this was closed. The notification mail is below, but you're telling me it's correct, and I should look at build.log.gz. But if you look at the example, the compilation messages are actually in build.log for failed builds. Successful builds do have the messages in build.log.gz. If I'm supposed to look at different logs depending on whether or not the build failed, I think that should be changed to avoid confusing users and potentially allow automation. ---------- From: <notifications> Subject: loveshack's livhpc copr build of proot-5.1.0-6.git803e54d.el7 for epel-7-aarch64 finished with 'failed' To: <loveshack> Date: Tue, 1 Oct 2019 08:31:54 +0000 (3 days, 5 hours, 23 minutes ago) Notification time stamped 2019-10-01 08:31:52 UTC Package: proot-5.1.0-6.git803e54d.el7 COPR: loveshack/livhpc Built by: loveshack Status: failed ID: 01042960 Logs: Build: https://copr-be.cloud.fedoraproject.org/results/loveshack/livhpc/epel-7-aarch64/01042960-proot/build.log.gz Root: https://copr-be.cloud.fedoraproject.org/results/loveshack/livhpc/epel-7-aarch64/01042960-proot/root.log.gz Copr: https://copr-be.cloud.fedoraproject.org/results/loveshack/livhpc/epel-7-aarch64/build-01042960.log Mockchain: https://copr-be.cloud.fedoraproject.org/results/loveshack/livhpc/epel-7-aarch64/01042960-proot/mockchain.log.gz Results: https://copr-be.cloud.fedoraproject.org/results/loveshack/livhpc/epel-7-aarch64/01042960-proot/ Repodata: https://copr-be.cloud.fedoraproject.org/results/loveshack/livhpc/epel-7-aarch64/repodata/ https://copr.fedoraproject.org/coprs/loveshack/livhpc/build/1042960/
So we need to fix fedora notification emails somewhere, so they only provide the link to `builder-live.log.gz`, nothing else. But I'm not sure who to contact about this ATM.
Ok, got it. This is caused by broken mock, but fixed in git master: https://github.com/rpm-software-management/mock/pull/368/files The reason seem to be that in case of failure (exception), the postbuild hooks has no chance to be executed. Once there's a new mock release, even failed builds will have compressed logs.
Is fixed on copr , I think it is fixed with Mock Version: 1.4.21
Yes, right. I forgot to link it to bodhi update,