[PATCH v3 0/8] Add support for tests "checks"

Finucane, Stephen stephen.finucane at intel.com
Fri Nov 6 04:18:31 AEDT 2015

> This series introduces support for patch "checks". These are results
> of tests and other automated checks executed on any given patch. Such
> tests and checks can range from unit tests and license validation to
> large integration and performance testing. These statuses can be
> provided by multiple users, thus allowing for a "distibuted test
> infrastructure".
> This feature requires a number of changes, such as new models and
> extensions to the templates. Some new "endpoints" are provided for the
> XML-RPC API along with a minimal extension to the 'pwclient'
> application. It is envisioned that both this application and the
> broader collection of scripts provided with patchwork will be expanded
> on by the community as required.
> This feature is entirely optional and can be ignored by users if so
> desired.
> v3:
> - Merge with Web UI rework
> - Remove already-upstreamed patches
> - Remove manual SQL migrations, which are not necessary now that Django
>   1.6 support have been removed.
> v2:
> - Rename 'status' to 'check' to prevent confusion with 'state'

Like the web UI rework, this has been sitting in the mailing list long that I'm happy to merge. While there are still open discussions RE: emailing of combined statuses, this functionality can be achieved outside of Patchwork and can be added in a future change. By sheer number of +1s to -1s, LGTM.


More information about the Patchwork mailing list