distributed tests of a patch

Finucane, Stephen stephen.finucane at intel.com
Fri Jul 24 01:24:34 AEST 2015

> On 7/23/15 10:49 AM, Thomas Monjalon wrote:
> > Hi,
> >
> > Thanks Thomas Herbert and Stephen Finucane for the help and the previous
> > offline discussions.
> >
> > 2015-07-23 10:13, Thomas F Herbert:
> >> Second: We will add a column to the main page showing test status for
> >> each patch ID with three counts for Success/Warning/Error
> >>
> >> Third: We will be updating the patch detailed view analogously to
> >> "headers show" with summary descriptions of the submittted test results.
> >>
> >> Fourth: We will have an additional new main page showing "incoming test
> >> results" indexed by patch_id with a list of incoming test results.
> >> Clicking on each test result will show the longer test results generally
> >> Jenkins console dumps (However there is nothing in this proposal that
> >> maintains Jenkins or any other CI tool)
> >
> > Why this fourth change is needed?
> ThomasM is correct and I retract my fourth change above. It is not
> needed because the test results are submitted by email as described
> above by ThomasM. Patchwork will only need to display a link to wherever
> the email is archived.

I would suggest adding one more:

Sixth (fifth?): An option will be added to the 'project' model to enable/disable CI support (defaulting to disabled in the migration script, but enabled in the Django Admin wizard). This exists for the new tag feature so we should probably add it for this.


More information about the Patchwork mailing list