On Friday, September 6, 2019 11:32:21 AM CEST Miroslav Suchý wrote:
> Dne 05. 09. 19 v 17:09 Pavel Raiskup napsal(a):
> > Hm, this is weird.  From what I can tell, there should be only 3 (log) 
> > files in
> > that directories (or Nx3 files).  What exactly is linkable there?
> 
> 
> Hmm, this was just mistake cause by formating of output. My fault.
> 
> >> 2) srpm_build/ - it has the same tar ball for resubmits
> > Weird as well, there shouldn't be tarballs but source RPMs, and since we 
> > don't
> > have reproducible builds - those files shouldn't be linkable.
> 
> # pwd
> /var/lib/copr/public_html/results/@python/python3.8/srpm-builds
> [root@copr-be srpm-builds][PROD]# find -name astrometry-data-4206.tar.xz |head
> ./00953171/astrometry-data-4206.tar.xz
> ./00955002/astrometry-data-4206.tar.xz
> ./00953380/astrometry-data-4206.tar.xz
> ./00963734/astrometry-data-4206.tar.xz
> ./00951719/astrometry-data-4206.tar.xz
> ./00951765/astrometry-data-4206.tar.xz
> ./00951697/astrometry-data-4206.tar.xz
> ./00951952/astrometry-data-4206.tar.xz
> ./00951709/astrometry-data-4206.tar.xz
> ./00952065/astrometry-data-4206.tar.xz

Thanks, interesting, from builder-live.log:

RPM build errors:
stderr: error: create archive failed on file 
/var/lib/copr-rpmbuild/resultsm05t6tgz/astrometry-data-4204.tar.xz: cpio: write 
failed - No space left on device
    create archive failed on file 
/var/lib/copr-rpmbuild/resultsm05t6tgz/astrometry-data-4204.tar.xz: cpio: write 
failed - No space left on device
Failed to execute command.

So this is caused by error case, when the tarball is packaged into
src.rpm.  Hmm, hopefully not very frequent case :-(

Pavel


_______________________________________________
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]

Reply via email to