Copr success but no packages?

[Steven A. Falco]

I ran the following build on Copr:

https://copr.fedorainfracloud.org/coprs/stevenfalco/kicad/build/3123050/

There are three chroots, one for F34, F35, and rawhide (all x86_64).

All report "success", but there are no resulting rpm packages in the F35 area. 
The F34 and rawhide areas look correct and have rpm packages.

Here are direct links to the chroots:

https://download.copr.fedorainfracloud.org/results/stevenfalco/kicad/fedo...

https://download.copr.fedorainfracloud.org/results/stevenfalco/kicad/fedo...

https://download.copr.fedorainfracloud.org/results/stevenfalco/kicad/fedo...

The builder-live.log in the F35 dir shows that the rpms were written, but they are missing
from the dir.

Can someone with root access to the copr infra please take a look?

	Thanks,
	Steve

[Elliott Sales de Andrade]

On Mon, 3 Jan 2022 at 16:25, Steven A. Falco <stevenfalco(a)gmail.com&gt; wrote:
>  I ran the following build on Copr:
>
>  https://copr.fedorainfracloud.org/coprs/stevenfalco/kicad/build/3123050/
>
>  There are three chroots, one for F34, F35, and rawhide (all x86_64).
>
>  All report "success", but there are no resulting rpm packages in the F35 area. 
> The F34 and rawhide areas look correct and have rpm packages.
>  
Do you need to force-refresh the page?

>  Here are direct links to the chroots:
>
>
> https://download.copr.fedorainfracloud.org/results/stevenfalco/kicad/fedo...
>
>
> https://download.copr.fedorainfracloud.org/results/stevenfalco/kicad/fedo...
>  
I see:
kicad-6.0.0-2.fc35.src.rpm 2022-Jan-03 19:16:50 719.50M RPM File
kicad-6.0.0-2.fc35.x86_64.rpm 2022-Jan-03 19:16:52 50.74M RPM File
kicad-debuginfo-6.0.0-2.fc35.x86_64.rpm 2022-Jan-03 19:16:43 283.27M RPM File
kicad-debugsource-6.0.0-2.fc35.x86_64.rpm 2022-Jan-03 19:16:59 5.85M RPM File
kicad-doc-6.0.0-2.fc35.noarch.rpm 2022-Jan-03 19:16:58 109.90M RPM File
kicad-packages3d-6.0.0-2.fc35.noarch.rpm 2022-Jan-03 19:16:56 385.23M RPM File

> https://download.copr.fedorainfracloud.org/results/stevenfalco/kicad/fedo...
>
>  The builder-live.log in the F35 dir shows that the rpms were written, but they are
> missing from the dir.
>
>  Can someone with root access to the copr infra please take a look?
>
>          Thanks,
>          Steve 
-- 
Elliott

[Steven A. Falco]

On 1/3/22 04:38 PM, Elliott Sales de Andrade wrote:
>  On Mon, 3 Jan 2022 at 16:25, Steven A. Falco
> <stevenfalco(a)gmail.com&gt; wrote:
> >
> > I ran the following build on Copr:
> >
> > https://copr.fedorainfracloud.org/coprs/stevenfalco/kicad/build/3123050/
> >
> > There are three chroots, one for F34, F35, and rawhide (all x86_64).
> >
> > All report "success", but there are no resulting rpm packages in the F35
> area.  The F34 and rawhide areas look correct and have rpm packages.
> >
>  
>  Do you need to force-refresh the page?
>  
> > Here are direct links to the chroots:
> >
> >
> https://download.copr.fedorainfracloud.org/results/stevenfalco/kicad/fedo...
> >
> >
> https://download.copr.fedorainfracloud.org/results/stevenfalco/kicad/fedo...
> >
>  
>  I see:
>  kicad-6.0.0-2.fc35.src.rpm 2022-Jan-03 19:16:50 719.50M RPM File
>  kicad-6.0.0-2.fc35.x86_64.rpm 2022-Jan-03 19:16:52 50.74M RPM File
>  kicad-debuginfo-6.0.0-2.fc35.x86_64.rpm 2022-Jan-03 19:16:43 283.27M RPM File
>  kicad-debugsource-6.0.0-2.fc35.x86_64.rpm 2022-Jan-03 19:16:59 5.85M RPM File
>  kicad-doc-6.0.0-2.fc35.noarch.rpm 2022-Jan-03 19:16:58 109.90M RPM File
>  kicad-packages3d-6.0.0-2.fc35.noarch.rpm 2022-Jan-03 19:16:56 385.23M RPM File 
That is very strange.  I tried that link with three different browsers: Firefox,
Konqueror, and Chrome, and I don't see the files on any of them.  I even tried using
my smart phone, and all I see are three log files: backend.log, build.log, and
builder-live.log.

But then I tried a different link:

https://copr-be.cloud.fedoraproject.org/results/stevenfalco/kicad/fedora-...

and there I see the files.  So they must really be there, but the link is not working for
me.  And no, I'm not running some sort of caching firewall.

I don't see how the problem can be on my end if all those separate browsers show the
same bad result.  But I guess it could be a caching issue somewhere else.

	Steve

[Miroslav Suchý]

Dne 03. 01. 22 v 22:57 Steven A. Falco napsal(a):
>  On 1/3/22 04:38 PM, Elliott Sales de Andrade wrote:
> > Here are direct links to the chroots:
> >>
> >>
> https://download.copr.fedorainfracloud.org/results/stevenfalco/kicad/fedo...
> >>
> >>
> https://download.copr.fedorainfracloud.org/results/stevenfalco/kicad/fedo...
>  But then I tried a different link:
>
>
> https://copr-be.cloud.fedoraproject.org/results/stevenfalco/kicad/fedora-...
>
>  and there I see the files.  So they must really be there, but the link is not working for
> me.  And no, I'm not running 
>  some sort of caching firewall. 
The download.copr.f.o are cnames to CDN all around the world (provided by AWS).

copr-be.cloud.f.o is the real name of the server.

So I guess it is may be some CDN issue. Which is pain to investigate/replicate.

Miroslav

[Pavel Raiskup]

On Tuesday, January 4, 2022 8:51:58 AM CET Miroslav Suchý wrote:
>  Dne 03. 01. 22 v 22:57 Steven A. Falco napsal(a):
>  > On 1/3/22 04:38 PM, Elliott Sales de Andrade wrote:
>  >> Here are direct links to the chroots:
>  >>>
>  >>>
> https://download.copr.fedorainfracloud.org/results/stevenfalco/kicad/fedo...
>  >>>
>  >>>
> https://download.copr.fedorainfracloud.org/results/stevenfalco/kicad/fedo...
>  > But then I tried a different link:
>  >
>  >
> https://copr-be.cloud.fedoraproject.org/results/stevenfalco/kicad/fedora-...
>  >
>  > and there I see the files.  So they must really be there, but the link is not
> working for me.  And no, I'm not running 
>  > some sort of caching firewall.
>  
>  The download.copr.f.o are cnames to CDN all around the world (provided by AWS).
>  
>  copr-be.cloud.f.o is the real name of the server.
>  
>  So I guess it is may be some CDN issue. Which is pain to investigate/replicate. 
We documented the CDN problem some time ago [1]:

| Build succeeded, but I don’t see the built results? ¶
| 
| Fedora Copr uses the AWS CDN to spread the HTTP traffic on the built RPM
| repositories across the globe, and it implies a lot of caching on the AWS side.
| 
| When you (or anyone else in your territory) check the build directory while the
| build is still in progress, the web server directory listing gets cached in CDN
| - and then the contents of the directory appears unchanged for some time (even
| though the build might already be finished and thus the directory updated).
| 
| Don’t worry, this caching doesn’t affect the DNF/YUM behavior - so even though
| your browser is misled by caches, package managers always download the latest
| contents of the directories. Either please ignore the inconsistency, or visit
| the non-cached host variant.


[1]
https://docs.pagure.org/copr.copr/user_documentation.html#build-succeeded...

Pavel

>  Miroslav
>  
>  _______________________________________________
>  devel mailing list -- devel(a)lists.fedoraproject.org
>  To unsubscribe send an email to devel-leave(a)lists.fedoraproject.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.fedoraproject.org/archives/list/[e-mail]
>  Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
>

[Alexander Ploumistos]

Hi Steve,

It looks like you had some (browser?) caching issue, all the rpms in
all the chroots are there.


Best regards,
A.

[Vitaly Zaitsev]

On 03/01/2022 22:25, Steven A. Falco wrote:
>  The builder-live.log in the F35 dir shows that the rpms were written,
>
>  but they are missing from the dir. 
Too aggressive web cache on COPR side. I've seen this issue several 
times too.

-- 
Sincerely,
   Vitaly Zaitsev (vitaly(a)easycoding.org)

[Steven A. Falco]

On 1/4/22 04:28 AM, Vitaly Zaitsev via devel wrote:
>  On 03/01/2022 22:25, Steven A. Falco wrote:
> > The builder-live.log in the F35 dir shows that the rpms were written, but they are
> missing from the dir.
>  
>  Too aggressive web cache on COPR side. I've seen this issue several times too.
Thanks for all the replies.  It is unfortunate, but now that I have a work-around I can
live with it.

	Steve