[Patchew-devel] [PATCH 0/3] A few testing related fixes

Fam Zheng posted 3 patches 5 weeks ago
Patches applied successfully (tree, apply log)
git fetch https://github.com/patchew-project/patchew-ci tags/patchew/20181031012429.25415-1-famz@redhat.com
api/views.py          | 11 +++++++++++
mod.py                | 10 ++++------
mods/testing.py       |  8 ++++++++
tests/test_testing.py | 19 +++++++++++++++++++
4 files changed, 42 insertions(+), 6 deletions(-)

[Patchew-devel] [PATCH 0/3] A few testing related fixes

Posted by Fam Zheng 5 weeks ago
The first two are already on patchew.org for a while worked as urgent hotfixes.
The last is the fix for the bug that prevents deletion of testings on the web
interface.

Fam Zheng (3):
  testing: Fix assert failure about git result
  testing: Recalculate pending tests after disabling tests
  Rework map entry delete

 api/views.py          | 11 +++++++++++
 mod.py                | 10 ++++------
 mods/testing.py       |  8 ++++++++
 tests/test_testing.py | 19 +++++++++++++++++++
 4 files changed, 42 insertions(+), 6 deletions(-)

-- 
2.17.2

_______________________________________________
Patchew-devel mailing list
Patchew-devel@redhat.com
https://www.redhat.com/mailman/listinfo/patchew-devel

Re: [Patchew-devel] [PATCH 0/3] A few testing related fixes

Posted by Paolo Bonzini 5 weeks ago
On 31/10/2018 02:24, Fam Zheng wrote:
> The first two are already on patchew.org for a while worked as urgent hotfixes.
> The last is the fix for the bug that prevents deletion of testings on the web
> interface.
> 
> Fam Zheng (3):
>   testing: Fix assert failure about git result
>   testing: Recalculate pending tests after disabling tests
>   Rework map entry delete
> 
>  api/views.py          | 11 +++++++++++
>  mod.py                | 10 ++++------
>  mods/testing.py       |  8 ++++++++
>  tests/test_testing.py | 19 +++++++++++++++++++
>  4 files changed, 42 insertions(+), 6 deletions(-)
> 

I pushed 1 and 3, thanks!  One urgent-ish thing to do is to make
next.patchew.org pull from the next branch, so that these urgent
bugfixes can be public on the patchew git tree.  Issues can be filed to
fix them properly in next, whenever needed.

Paolo

_______________________________________________
Patchew-devel mailing list
Patchew-devel@redhat.com
https://www.redhat.com/mailman/listinfo/patchew-devel

Re: [Patchew-devel] [PATCH 0/3] A few testing related fixes

Posted by Fam Zheng 5 weeks ago
On Wed, 10/31 13:38, Paolo Bonzini wrote:
> On 31/10/2018 02:24, Fam Zheng wrote:
> > The first two are already on patchew.org for a while worked as urgent hotfixes.
> > The last is the fix for the bug that prevents deletion of testings on the web
> > interface.
> > 
> > Fam Zheng (3):
> >   testing: Fix assert failure about git result
> >   testing: Recalculate pending tests after disabling tests
> >   Rework map entry delete
> > 
> >  api/views.py          | 11 +++++++++++
> >  mod.py                | 10 ++++------
> >  mods/testing.py       |  8 ++++++++
> >  tests/test_testing.py | 19 +++++++++++++++++++
> >  4 files changed, 42 insertions(+), 6 deletions(-)
> > 
> 
> I pushed 1 and 3, thanks!  One urgent-ish thing to do is to make
> next.patchew.org pull from the next branch, so that these urgent
> bugfixes can be public on the patchew git tree.  Issues can be filed to
> fix them properly in next, whenever needed.

Then, how do master and next work exactly? Do you mean next.patchew.org follows
'next' and patchew.org follows 'master', and we merge next stuff to master after
reviewing and testing?

Fam

_______________________________________________
Patchew-devel mailing list
Patchew-devel@redhat.com
https://www.redhat.com/mailman/listinfo/patchew-devel

Re: [Patchew-devel] [PATCH 0/3] A few testing related fixes

Posted by Paolo Bonzini 5 weeks ago
On 01/11/2018 07:36, Fam Zheng wrote:
> On Wed, 10/31 13:38, Paolo Bonzini wrote:
>> On 31/10/2018 02:24, Fam Zheng wrote:
>>> The first two are already on patchew.org for a while worked as urgent hotfixes.
>>> The last is the fix for the bug that prevents deletion of testings on the web
>>> interface.
>>>
>>> Fam Zheng (3):
>>>   testing: Fix assert failure about git result
>>>   testing: Recalculate pending tests after disabling tests
>>>   Rework map entry delete
>>>
>>>  api/views.py          | 11 +++++++++++
>>>  mod.py                | 10 ++++------
>>>  mods/testing.py       |  8 ++++++++
>>>  tests/test_testing.py | 19 +++++++++++++++++++
>>>  4 files changed, 42 insertions(+), 6 deletions(-)
>>>
>>
>> I pushed 1 and 3, thanks!  One urgent-ish thing to do is to make
>> next.patchew.org pull from the next branch, so that these urgent
>> bugfixes can be public on the patchew git tree.  Issues can be filed to
>> fix them properly in next, whenever needed.
> 
> Then, how do master and next work exactly? Do you mean next.patchew.org follows
> 'next' and patchew.org follows 'master', and we merge next stuff to master after
> reviewing and testing?

Yes, exactly.  And if something slips, we can fix it quickly on 'master'.

Paolo

_______________________________________________
Patchew-devel mailing list
Patchew-devel@redhat.com
https://www.redhat.com/mailman/listinfo/patchew-devel