Fedora Copr Outage - Updating to a March 2024 Version

[Pavel Raiskup]

There will be a Fedora Copr outage starting at

$ date --date '2024-03-07 11:30 UTC'

The outage will last approximately 2 hours. The build queue processing will
be stopped during the outage, and the Frontend/Web-UI will be down most of
the time (no new tasks accepted).

The DNF packages and repositories (hosted on copr-backend) will be available
during this outage.

Reason for outage:
We will update the infrastructure machines to the latest packages that are
currently being developed.

Affected Services:
https://copr.fedorainfracloud.org/
https://download.copr.fedorainfracloud.org/results/

Upstream ticket:
https://github.com/fedora-copr/copr/issues/3151

Infrastructure ticket:
https://pagure.io/fedora-infrastructure/issue/11808

Please join Fedora Build System Matrix channel:
https://matrix.to/#/#buildsys:fedoraproject.org

Outage Contacts:
@praiskup (Pavel Raiskup) / @frostyx (Jakub Kadlčík)

[Pavel Raiskup]

And the outage is over.  Release notes here:

https://docs.pagure.org/copr.copr/release-notes/2024-03-07.html

Special Highlight: Jakub added an exciting new feature in this release,
allowing users to SSH to Copr builders.  This is exciting news!

Happy building!
Pavel

On pondělí 4. března 2024 17:53:13 CET Pavel Raiskup wrote:
> There will be a Fedora Copr outage starting at
> $ date --date '2024-03-07 11:30 UTC'
>
> The outage will last approximately 2 hours. The build queue processing will
> be stopped during the outage, and the Frontend/Web-UI will be down most of
> the time (no new tasks accepted).
>
> The DNF packages and repositories (hosted on copr-backend) will be available
> during this outage.
>
> Reason for outage:
> We will update the infrastructure machines to the latest packages that are
> currently being developed.
>
> Affected Services:
> https://copr.fedorainfracloud.org/
> https://download.copr.fedorainfracloud.org/results/
>
> Upstream ticket:
> https://github.com/fedora-copr/copr/issues/3151
>
> Infrastructure ticket:
> https://pagure.io/fedora-infrastructure/issue/11808
>
> Please join Fedora Build System Matrix channel:
> https://matrix.to/#/#buildsys:fedoraproject.org
>
> Outage Contacts:
> @praiskup (Pavel Raiskup) / @frostyx (Jakub Kadlčík)

[Michael J Gruber]

Am Do., 7. März 2024 um 13:09 Uhr schrieb Pavel Raiskup :
> And the outage is over.  Release notes here:
> https://docs.pagure.org/copr.copr/release-notes/2024-03-07.html
>
> Special Highlight: Jakub added an exciting new feature in this release,
> allowing users to SSH to Copr builders.  This is exciting news!
>
> Happy building!
> Pavel

Thanks, that is neat indeed :)

Would it make sense to have the "rebuild with ssh access" call mock
with "--no-clean-after"? Without that, there is not that much more to
inspect than the chroot itself, is there? Or is the idea that we run
mock again?

Michael

[Pavel Raiskup]

Hello Michael,

On čtvrtek 7. března 2024 16:31:14 CET Michael J Gruber wrote:
> Am Do., 7. März 2024 um 13:09 Uhr schrieb Pavel Raiskup :
> > And the outage is over.  Release notes here:
> > https://docs.pagure.org/copr.copr/release-notes/2024-03-07.html
> >
> > Special Highlight: Jakub added an exciting new feature in this release,
> > allowing users to SSH to Copr builders.  This is exciting news!
> >
> > Happy building!
> > Pavel
>
> Thanks, that is neat indeed :)
>
> Would it make sense to have the "rebuild with ssh access" call mock
> with "--no-clean-after"? Without that, there is not that much more to
> inspect than the chroot itself, is there? Or is the idea that we run
> mock again?

Yes, we originally meant that the build would be resubmitted.  Though
the idea with --no-clean-after sounds like a reasonable RFE ;) Feel free
to open a ticket https://github.com/fedora-copr/copr/issues

Pavel
> Michael
>
> copr-devel mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> 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/[e-mail].o...
> Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

[Miroslav Suchý]

Dne 09. 03. 24 v 11:13 Pavel Raiskup napsal(a):
> Would it make sense to have the "rebuild with ssh access" call mock
> with "--no-clean-after"? Without that, there is not that much more to
> inspect than the chroot itself, is there? Or is the idea that we run
> mock again?

The idea, is that you will be able to execute the command in the chroot.

So instead of building packages in mode "try this" and "try that", you will be able to run e.g. gcc in that chroot. 
Maybe put there some print() for debugging. To find the culprit of failure faster. Especially on non-intel architectures.