#2338 builder-live.log says successful but backend.log fails with error code 124
Closed: Won't fix 3 years ago by praiskup. Opened 3 years ago by mtasaka.

Recently I've seen many cases where builder-live.log.gz says rpmbuild (rebuild) finishes successfully, but backend.log.gz says although "copr-rpmbuild" is successful later "copr-repo" failed so the whole task finished unsuccessfully:

For example:
https://copr.fedorainfracloud.org/coprs/mtasaka/rubygem-newruby-test/build/4899887/
https://copr.fedorainfracloud.org/coprs/mtasaka/rubygem-newruby-test/build/4899939/

Would you investigate what is happening?


Would you investigate what is happening?

Sure, thank you for the report.

Seems like your project got reasonably large and the appstream-builder isn't able to finish quickly enough (in 10 minutes). Therefore the build timeouts, and fails. Errors can be found in the backend.log.

Please disable the appstream metadata feature for your project. We have no tool to generate the metadata in Copr (we re-build DNF metadata after each package build).

Some related documentation:
https://docs.pagure.org/copr.copr/user_documentation.html#mass-rebuilds

Metadata Update from @praiskup:
- Issue close_status updated to: Won't fix
- Issue status updated to: Closed (was: Open)

3 years ago

Log in to comment on this ticket.

Metadata