[PULL] github.com/stephenfin/development

[Damien Lespiau]

On Fri, Oct 16, 2015 at 07:08:45PM +0100, Finucane, Stephen wrote:
> # 1) Add additional project configuration options:
> 
> We should add the following options to the 'Project' model
> 
>  * Add an optional list property to specify the tests contexts that
>  have to run in order for a patch to be marked as "testing complete".
>  If set, an email will be sent on test completion. If unset, no emails
>  will be sent and Thomas' process can be used
>  * Add a Boolean property to state whether to restrict results to
>  these contexts only or whether to allow any and all contexts (but
>  basically ignore the ones not in the list)
>  * Add a Boolean property to restrict publishing of 'checks' to
>  maintainers or to all patchwork users. This can be expanded on later
>  (see below)
>  * [OPTIONAL] Add an option to turn 'Check' support on/off. Some
>  people won't want the extra column in the summary field cluttering
>  their view. This should be set to 'enabled' (i.e. use 'Checks') by
>  default, IMO.

So now, I want to add the feature I already talked about: configure how
result emails should be sent:

  - static tests like checkpatch.pl or sparse: only send emails on
    failure
  - long running tests (hours, 10s of hours) like piglit[1] or
    intel-gpu-tools[2]: always send result emails

How would that fit in this model? I still think real test objects,
disregarding how it's created, are the way to be more future-proof.

However, I'm afraid I don't really have the time to discuss this any
further. So don't let me block anything.

-- 
Damien

[1] http://cgit.freedesktop.org/piglit/
[2] http://cgit.freedesktop.org/xorg/app/intel-gpu-tools/