Re: [PATCH 00/10] Add support for tests statuses

On Wed, Jul 29, 2015 at 12:14:54PM +0200, Thomas Monjalon wrote: Hi Thomas, 2015-07-29 11:53, Thomas Petazzoni: On Wed, 29 Jul 2015 09:58:38 +0100, Stephen Finucane wrote: This series introduces support for patch statuses. These are results of tests and other automated checks executed

[PATCH 05/10] models: Add properties related to status

Add properties for 'Patch' to get the unique statuses associated with a patch, the total number of each type of status and the combined state of the statuses. These will be necessary to display this information to the user. Signed-off-by: Stephen Finucane stephen.finuc...@intel.com ---

[PATCH 03/10] trivial: Cleanup of 'admin.py'

Resolve some issues with the aforementioned file. These are mostly stylistic changes. In addition, add a missing license. The date and author are calculated from Git logs. Signed-off-by: Stephen Finucane stephen.finuc...@intel.com --- patchwork/admin.py | 41

[PATCH 06/10] templates/patch-list: Add patch status column

Add a column to display the important status fields for each patch. Note that only the completed statuses are shown (i.e. in progress and not started statuses are ignored). Signed-off-by: Stephen Finucane stephen.finuc...@intel.com --- patchwork/templates/patchwork/patch-list.html | 5 +

[PATCH 02/10] trivial: Cleanup of 'models.py'

From: Stephen Finucane stephenfinuc...@hotmail.com Resolve some issues with the aforementioned file. These are mostly stylistic changes. Signed-off-by: Stephen Finucane stephen.finuc...@intel.com --- patchwork/models.py | 228 1 file changed,

[PATCH 10/10] pwclient: Integrate 'status' endpoint

Signed-off-by: Stephen Finucane stephen.finuc...@intel.com --- patchwork/bin/pwclient | 14 ++ 1 file changed, 14 insertions(+) diff --git a/patchwork/bin/pwclient b/patchwork/bin/pwclient index 8d1f476..bcb0293 100755 --- a/patchwork/bin/pwclient +++ b/patchwork/bin/pwclient @@

Re: [PATCH 04/10] models: Add 'status' model

Hi Stephen, Thanks for your good work. 2015-07-29 09:58, Stephen Finucane: +class Status(models.Model): +Status for a patch. + +Statuses define a state for patches. This is useful, for example, +when using a continuous integration (CI) system to test patches. + There is

[PATCH 01/10] models: Resolve issues with Patch.state

The initial migration was incomplete: running 'makemigrations' on the current codebase would produce a migration which could not be applied. Fix this issue and add a suitable migration to resolve the issue henceforth. Signed-off-by: Stephen Finucane stephen.finuc...@intel.com ---

[PATCH 00/10] Add support for tests statuses

This series introduces support for patch statuses. 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

[PATCH 04/10] models: Add 'status' model

From: Stephen Finucane stephenfinuc...@hotmail.com This will represent the status of a patch. This includes a suitable migration and admin view. Signed-off-by: Stephen Finucane stephenfinuc...@hotmail.com --- lib/sql/grant-all.mysql.sql | 5 +-- lib/sql/grant-all.postgres.sql

[PATCH 08/10] trivial: Clean up 'views/xmlrpc.py'

From: Stephen Finucane stephenfinuc...@hotmail.com Resolve some issues with the aforementioned file. These are mostly stylistic changes. Signed-off-by: Stephen Finucane stephenfinuc...@hotmail.com --- patchwork/views/xmlrpc.py | 319 -- 1 file

Re: [PATCH 00/10] Add support for tests statuses

Hi Thomas, 2015-07-29 11:53, Thomas Petazzoni: On Wed, 29 Jul 2015 09:58:38 +0100, Stephen Finucane wrote: This series introduces support for patch statuses. These are results of tests and other automated checks executed on any given patch. Such tests and checks can range from unit tests

RE: [PATCH 00/10] Add support for tests statuses

Stephen, On Wed, 29 Jul 2015 09:58:38 +0100, Stephen Finucane wrote: This series introduces support for patch statuses. 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

Re: [PATCH 04/10] models: Add 'status' model

2015-07-29 13:33, Finucane, Stephen: Having State and Status is confusing. What about getting rid of State? :) I haven't found any public patchwork project that modifies the default list of states, so I think a static choices field on 'Patch' would be a better option. I actually have a

RE: [PATCH 04/10] models: Add 'status' model

2015-07-29 09:58, Finucane, Stephen: 2015-07-29 09:58, Stephen Finucane: +class Status(models.Model): +Status for a patch. + +Statuses define a state for patches. This is useful, for example, +when using a continuous integration (CI) system to test patches.