From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: Arkadiusz Hiler <arkadiusz.hiler@intel.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: [QUERY] How many CI mails is too many?
Date: Tue, 28 Nov 2017 10:15:13 +0200 [thread overview]
Message-ID: <1511856913.4761.5.camel@linux.intel.com> (raw)
In-Reply-To: <20171127145402.GA19994@ahiler-desk1.ger.corp.intel.com>
On Mon, 2017-11-27 at 16:54 +0200, Arkadiusz Hiler wrote:
> Hey all,
>
> For some time already CI sends out 1-2 mails per series per (re)run, i.e. BAT
> results and "full IGT" results (if BAT has not failed).
>
> Recently we have added 32bit build check, and if that fails it sends out
> additional mail In-Reply-To the series.
>
> I am working on adding some static checks to the CI (spare and checkpatch at the
> moment, more may come in the future), which may generate even more commotion on
> the mailing list.
>
> How much of CI noise is too much and how you would like to have the results
> grouped?
>
> Couple of options to start the discussion:
>
> 1. Group all static checks (and the 32bit build?) into one mail:
> - just one additional mail,
> - may be hard to read in case of catastrophic failure,
> - we can send it only when something actually fails.
>
> 2. Send out the results as a part of BAT results:
> - even less noise than (1),
> - BAT results already feel cluttered, this may decrease readability.
>
> 3. Have each check as a separate mail, but send it only if the check fails:
> - noisy: may result in many mails, depending how many checks fail,
> - easier to read and easier to follow on patchwork.
The best user experience I could think of;
1. If all CI checks succeed, delay and only send one mail with all the
results. This would indicate it's good to merge, go do it.
2. When a CI checks fail, immediately send that out so the developer
gets to work on the fix.
Above requires that all the checks complete rather quickly and a trust
is gained to the system so that the absence of e-mail always means the
series is doing good, not that the system is clogged in some way :)
Regards, Joonas
>
> Any opinions? Any other ideas?
>
--
Joonas Lahtinen
Open Source Technology Center
Intel Corporation
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-11-28 8:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-27 14:54 [QUERY] How many CI mails is too many? Arkadiusz Hiler
2017-11-27 15:40 ` Sagar Arun Kamble
2017-11-28 11:16 ` Arkadiusz Hiler
2017-11-29 9:24 ` Ewelina Musial
2017-11-27 20:27 ` Rodrigo Vivi
2017-11-28 8:15 ` Joonas Lahtinen [this message]
2017-11-28 10:06 ` Chris Wilson
2017-11-28 10:08 ` Daniel Vetter
2017-11-28 10:16 ` Chris Wilson
2017-11-29 9:48 ` Chris Wilson
2017-11-28 9:50 ` Tvrtko Ursulin
2017-11-28 9:54 ` Daniel Vetter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1511856913.4761.5.camel@linux.intel.com \
--to=joonas.lahtinen@linux.intel.com \
--cc=arkadiusz.hiler@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.