Re: [OE-core] [Openembedded-architecture] Patchwork and incoming patch testing

[Jose Lamego <jose.a.lamego@linux.intel.com>]

[-- Attachment #1.1: Type: text/plain, Size: 2564 bytes --]

I was replying to the wrong mailing list. Sorry for the spam. :(

On 01/18/2017 04:40 PM, Jose Lamego wrote:
> 
> On 01/18/2017 08:52 AM, Leonardo Sandoval wrote:
>> + Jose Lamego
>>
>>
>> Jose is doing recent work on the patchwork UI, perhaps there are already
>> bugs for the items you are asking.
>>
>>
>> On 01/18/2017 02:40 AM, Jussi Kukkonen wrote:
>>> This looks great, thanks.
>>>
>>> On 17 January 2017 at 20:05, Paul Eggleton
>>> <paul.eggleton@linux.intel.com <mailto:paul.eggleton@linux.intel.com>>
>>> wrote:
>>>
>>>     In any event we are now finally in the
>>>     position where our patchwork instance can be relied upon to
>>>     collect emails,
>>>     and the UI is much improved. This should give us a bit more
>>>     visibility into
>>>     where patches are at in the process, although we are still working
>>>     on a few
>>>     places where patch series status needs to be updated (e.g. when a
>>>     patch goes
>>>     into testing).
>>>
>>>
>>> What's the plan for these status updates -- is the idea that you go to
>>> patchwork UI to see the state of a specific patch set?
>>> Or maybe a reply to either patch sender or even the ML?
>>>
There is a request to enable email notifications to submitter for patch
status changes in the future:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=7684

The idea is that users should have the option to use what they prefer:
either the email notifications, or the patchwork web interface.
> 
>>>     On top of patchwork we have built a simple smoke-testing framework
>>>     called
>>>     "patchtest" [5] along with a suite of corresponding tests for OE
>>>     [6]. These
>>>     tests are fairly simplistic at this point but check the basics
>>>     such as whether
>>>     a patch has been properly signed off, etc. We should soon start
>>>     seeing replies
>>>     sent to the mailing list and to submitters with results if there
>>>     are any
>>>     failures, saving us from noticing and pointing out some of the
>>>     more obvious
>>>     classes of mistakes.
>>>
>>>
>>>  Is there a reason for patchwork only showing "success" or "failure"
>>> in the web ui, instead of linking to test results at least in in the
>>> failure case?
>>
>> Jussi, that is a good idea. Right now we need to click into the series,
>> then into the patches and then one can see the patch test results,
>> obviously, not the best way.
>>
>>>
>>>
>>>
>>>  - Jussi
>>>

-- 
Jose Lamego | OTC Embedded Platforms & Tools | GDC


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 501 bytes --]