<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 href="mailto:paul.eggleton@linux.intel.com" target="_blank">paul.eggleton@linux.intel.com</a>></span> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span style="font-size:12.8px">In any event we are now finally in the<br></span><span style="font-size:12.8px">position where our patchwork instance can be relied upon to collect emails,<br></span><span style="font-size:12.8px">and the UI is much improved. This should give us a bit more visibility into<br></span><span style="font-size:12.8px">where patches are at in the process, although we are still working on a few<br></span><span style="font-size:12.8px">places where patch series status needs to be updated (e.g. when a patch goes<br></span><span style="font-size:12.8px">into testing).</span></blockquote><div class="gmail_quote"><span style="font-size:12.8px"><br></span></div><div class="gmail_quote"><span style="font-size:12.8px">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 style="font-size:12.8px">Or maybe a reply to either patch sender or even the ML?</span></div><div class="gmail_quote"><span style="font-size:12.8px"><br></span></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">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><br></div><div><br></div><div><br></div><div> - Jussi</div><div><br></div></div></div></div>