Am 25.02.2022 um 23:19 schrieb Adam Williamson
<adamwill(a)fedoraproject.org>:
On Fri, 2022-02-25 at 22:35 +0100, Dan Čermák wrote:
> Hi Peter,
>
> Peter Boy <pboy(a)uni-bremen.de> writes:
>
>> Excuse my ignorance, but I'm just wondering what sense the regular rawhide
"compose check reports" make. Who processes this information?
>
> I am pretty certain that Adam and probably other members of Fedora's QA
> team review these reports and decide whether the compose is good to go
> or not.
Hi Dan,
I hope my wording did not have the wrong connotation. I didn't want to doubt the
usefulness, but to clarify if Server WG is expected to watch and to take care, or if
it's a pure information, and others like QA Team take care of it primarily (and
contact Server WG if necessary or helpful).
It's meant to give anyone who's interested a quick overview
of the
day's status, and anyone can review the results. The failed tests are
linked directly. If you find the volume a bit much, the topic is easy
to filter to a separate folder - this is what I do in fact (I filter
these reports and the "compose report" mails generated by releng to a
dedicated Reports folder).
When I have time I send a manual reply explaining the failures, but 36
and Rawhide have both been pretty chaotic lately so I haven't had time.
Very broadly, most tests are actually passing now, a few are affected
by known bugs. Most of interest to Server is that the aarch64 disk
images are affected by
https://bugzilla.redhat.com/show_bug.cgi?id=2057600 (initial-setup does
not run on first boot as it should).
Hi Adam,
thanks for the information. As you may have noticed I’ve initiated a discussion how to
contribute to improve Server release quality and to avoid some unpleasant experiences that
we had with the last releases. Those type of issues may not be detectable with automated
tests. Unfortunately, I lack an overview of the processes. I have never had any reason to
get familiar with them until now (unexpectedly having become somehow engaged in server
WG).
Peter