Hi Barry, thanks for the report.

On Saturday, March 7, 2020 12:50:09 PM CET Barry Scott wrote:
> I'm seeing build fail because of rsync problems.
> 
> https://download.copr.fedorainfracloud.org/results/barryascott/tools/epel-6-x86_64/01296960-bemacs/build-01296960.rsync.log
> 
> 
> Warning: Permanently added '54.83.156.162' (ECDSA) to the list of known hosts.
> receiving incremental file list
> rsync: link_stat "/var/lib/copr-rpmbuild/results/*" failed: No such file or 
> directory (2)
> 
> sent 8 bytes  received 101 bytes  218.00 bytes/sec
> total size is 0  speedup is 0.00
> rsync error: some files/attrs were not transferred (see previous errors) 
> (code 23) at main.c(1659) [Receiver=3.1.3]
> rsync: [Receiver] write error: Broken pipe (32)

It failed a bit sooner actually:
https://download.copr.fedorainfracloud.org/results/barryascott/tools/epel-6-x86_64/01296960-bemacs/builder-live.log.gz

> Is the infra having a problem or did I miss a step I should have done?

I tested epel-6 build now, and it worked fine.  I suppose the builder
suddently stopped responding, or become broken for some reason.  Can you please
retry?

Pavel

> Barry
> _______________________________________________
> copr-devel mailing list -- copr-devel@lists.fedorahosted.org
> To unsubscribe send an email to copr-devel-le...@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.fedorahosted.org
> 



_______________________________________________
copr-devel mailing list -- copr-devel@lists.fedorahosted.org
To unsubscribe send an email to copr-devel-le...@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.fedorahosted.org

Reply via email to