[Intel-gfx] [QUERY] How many CI mails is too many?
Daniel Vetter
daniel at ffwll.ch
Tue Nov 28 09:54:21 UTC 2017
On Mon, Nov 27, 2017 at 3:54 PM, Arkadiusz Hiler
<arkadiusz.hiler at intel.com> 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.
>
> Any opinions? Any other ideas?
All static checks grouped, and only sent out when there's something
iffy. I think for BAT&functional tests positive confirmation from CI
is good, but for static checkers it's a bit more meh imo. So 1&3 for
me.
And yes I'd group all the static checks and build checks into 1. E.g.
on dri-devel we also want to build-test arm and arm64 using the
drm-misc configs.
-Daniel
>
> --
> Cheers,
> Arek
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx at lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
More information about the Intel-gfx
mailing list