<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>+ Jose Lamego <br>
</p>
<p><br>
</p>
<p>Jose is doing recent work on the patchwork UI, perhaps there are
already bugs for the items you are asking.<br>
</p>
<br>
<div class="moz-cite-prefix">On 01/18/2017 02:40 AM, Jussi Kukkonen
wrote:<br>
</div>
<blockquote
cite="mid:CAHiDW_F=ybZibjGyjMpg4Gi+sEhSQPw6eVmGm7yxeUAj9mqFtQ@mail.gmail.com"
type="cite">
<meta http-equiv="Context-Type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div class="gmail_extra">
<div>This looks great, thanks.</div>
<div class="gmail_quote"><br>
</div>
<div class="gmail_quote">On 17 January 2017 at 20:05, Paul
Eggleton <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:paul.eggleton@linux.intel.com"
target="_blank">paul.eggleton@linux.intel.com</a>></span>
wrote:<br>
</div>
<blockquote class="gmail_quote"><span>In any event we are now
finally in the<br>
</span><span>position where our patchwork instance can be
relied upon to collect emails,<br>
</span><span>and the UI is much improved. This should give
us a bit more visibility into<br>
</span><span>where patches are at in the process, although
we are still working on a few<br>
</span><span>places where patch series status needs to be
updated (e.g. when a patch goes<br>
</span><span>into testing).</span></blockquote>
<div class="gmail_quote"><span><br>
</span></div>
<div class="gmail_quote"><span>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?</span></div>
<div class="gmail_quote"><span>Or maybe a reply to either
patch sender or even the ML?</span></div>
<div class="gmail_quote"><span><br>
</span></div>
<div class="gmail_quote">
<blockquote class="gmail_quote">On top of patchwork we have
built a simple smoke-testing framework called<br>
"patchtest" [5] along with a suite of corresponding tests
for OE [6]. These<br>
tests are fairly simplistic at this point but check the
basics such as whether<br>
a patch has been properly signed off, etc. We should soon
start seeing replies<br>
sent to the mailing list and to submitters with results if
there are any<br>
failures, saving us from noticing and pointing out some of
the more obvious<br>
classes of mistakes.</blockquote>
<div><br>
</div>
<div> 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?</div>
</div>
</div>
</div>
</blockquote>
<br>
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.<br>
<br>
<blockquote
cite="mid:CAHiDW_F=ybZibjGyjMpg4Gi+sEhSQPw6eVmGm7yxeUAj9mqFtQ@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote"><br>
<div><br>
</div>
<div><br>
</div>
<div> - Jussi</div>
<div><br>
</div>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
</blockquote>
<br>
</body>
</html>