DevHeads.net

Fedora testing-20190523.0 compose check report

Missing expected images:

Atomichost raw-xz x86_64
Atomichost qcow2 x86_64

Passed openQA tests: 2/2 (x86_64)

Comments

Re: Fedora testing-20190523.0 compose check report

By Christopher at 05/23/2019 - 20:32

Do these compose reports need to spam devel@ ?
I don't think most packagers are involved in composes, and it's hard
to follow devel@ when it's so busy. It's already cross-posting to
test@, that should be enough... perhaps there can be a composes@ list
for these? Then folks can opt in.

On Thu, May 23, 2019 at 5:44 PM Fedora compose checker
< ... at fedoraproject dot org> wrote:

Re: Fedora testing-20190523.0 compose check report

By Adam Williamson at 05/24/2019 - 11:10

On Thu, 2019-05-23 at 20:32 -0400, Christopher wrote:
Yes, they are. All packagers are involved in composes. Composes are
made from the packages built by packagers. :P Most of the bugs in
composes are caused by...bugs in packages.

Re: Fedora testing-20190523.0 compose check report

By Christopher at 05/24/2019 - 14:47

On Fri, May 24, 2019 at 11:11 AM Adam Williamson
< ... at fedoraproject dot org> wrote:
What I mean is that most packagers wouldn't know what to do with
these. These emails don't have any useful information for a packager
to follow up with. If there's a composition failure attributable to a
package, then those directly involved with composes, could easily pass
that information down to the relevant packager. I just think that more
automated notices that don't apply to *everyone* on the list, make it
harder for packagers to stay subscribed to the list. This kind of
information can easily be presented in a more friendly manner by doing
something like:

1. Provide a status webpage,
2. Publish to a subscribable service, like an RSS feed,
3. Put the automated emails to a separate composes@ or notifications@
list to allow opt-in.

It's nice to be able to keep the human-to-human conversations separate
from the bots. It's not critical... it's just nicer, and I think it
would help.

Re: Fedora testing-20190523.0 compose check report

By Chris Murphy at 05/23/2019 - 20:40

On Thu, May 23, 2019 at 6:33 PM Christopher < ... at fedoraproject dot org> wrote:
Matches: from:(<a href="mailto: ... at fedoraproject dot org"> ... at fedoraproject dot org</a>)
Do this: Mark as read, Delete it

Re: Fedora testing-20190523.0 compose check report

By Christopher at 05/24/2019 - 14:51

On Thu, May 23, 2019 at 8:42 PM Chris Murphy < ... at colorremedies dot com> wrote:
Are these are the only messages coming from that address?
I'm reluctant to do overly aggressive filtering, in case I miss
important things. I'm actually trying to be involved as much as I can.

Re: Fedora testing-20190523.0 compose check report

By Adam Williamson at 05/24/2019 - 15:19

On Fri, 2019-05-24 at 14:51 -0400, Christopher wrote:
Only automated report-type things are sent from that address. The
'compose report' emails (different from 'compose check report' emails)
and 'updates-testing report' mails also come from the same address.