Fedora testing-20190523.0 compose check report

[Fedora compose checker]

Missing expected images:

Atomichost raw-xz x86_64
Atomichost qcow2 x86_64

Passed openQA tests: 2/2 (x86_64)
-- 
Mail generated by check-compose:
https://pagure.io/fedora-qa/check-compose

[Christopher]

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
<rawhide(a)fedoraproject.org&gt; wrote:
>
> Missing expected images:
>
> Atomichost raw-xz x86_64
> Atomichost qcow2 x86_64
>
> Passed openQA tests: 2/2 (x86_64)
> --
> Mail generated by check-compose:
> https://pagure.io/fedora-qa/check-compose
> _______________________________________________
> 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://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
https://lists.fedoraproject.org/archives/list/[e-mail]

[Chris Murphy]

On Thu, May 23, 2019 at 6:33 PM Christopher <ctubbsii(a)fedoraproject.org&gt; wrote:
>  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. 
Matches: from:([e-mail])
Do this: Mark as read, Delete it


-- 
Chris Murphy

[Christopher]

On Thu, May 23, 2019 at 8:42 PM Chris Murphy <lists(a)colorremedies.com&gt; wrote:
>  On Thu, May 23, 2019 at 6:33 PM Christopher <ctubbsii(a)fedoraproject.org&gt; wrote:
>  >
>  > 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.
>
>  Matches: from:([e-mail])
>  Do this: Mark as read, Delete it
>  
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.

[Adam Williamson]

On Fri, 2019-05-24 at 14:51 -0400, Christopher wrote:
>  On Thu, May 23, 2019 at 8:42 PM Chris Murphy
> <lists(a)colorremedies.com&gt; wrote:
>  > On Thu, May 23, 2019 at 6:33 PM Christopher <ctubbsii(a)fedoraproject.org&gt;
> wrote:
>  > > 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.
>  > 
>  > Matches: from:([e-mail])
>  > Do this: Mark as read, Delete it
>  > 
>  
>  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. 
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.
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net

[Adam Williamson]

On Thu, 2019-05-23 at 20:32 -0400, Christopher wrote:
>  Do these compose reports need to spam devel@ ?
>  I don't think most packagers are involved in composes, 
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.
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net

[Christopher]

On Fri, May 24, 2019 at 11:11 AM Adam Williamson
<adamwill(a)fedoraproject.org&gt; wrote:
>  On Thu, 2019-05-23 at 20:32 -0400, Christopher wrote:
>  > Do these compose reports need to spam devel@ ?
>  > I don't think most packagers are involved in composes,
>
>  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. 
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.