<div dir="ltr">Please include me when you have the kick off meeting<div><br></div><div>Thanks,</div></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature" data-smartmail="gmail_signature">----------<br>Nancy</div></div>
<br><div class="gmail_quote">On Mon, Jul 23, 2018 at 6:51 AM, Sivas Srr <span dir="ltr"><<a href="mailto:sivas.srr@in.ibm.com" target="_blank">sivas.srr@in.ibm.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="m_8919110495936005460socmaildefaultfont" dir="ltr" style="font-family:Arial,Helvetica,sans-serif;font-size:10.5pt"><div dir="ltr">Thank you Brad Bishop (For offline review), Kurt Taylor and Andrew Geissler for your kind support.</div>
<div dir="ltr"> </div>
<div dir="ltr">Yes CI can be included.</div>
<div dir="ltr">( In my opinion, If we want to do good CI, we may have to do more left shift from CT bucket</div>
<div dir="ltr">as well). Dynamic CI, It should be. If major code drop associate with a feature/Area,</div>
<div dir="ltr">then test bucket of that CT bucket should be executed as part of CI. We can discuss on this.</div>
<div dir="ltr"> </div>
<div dir="ltr">For eg. IPMI user management features getting enabled then entire IPMI bucket can be run part of CI.</div>
<div dir="ltr"> </div>
<div dir="ltr">Test work group meeting:</div>
<div dir="ltr"> </div>
<div dir="ltr">As test based on release planning, Would like to have this meeting either on the same day after the release plan meeting or a day after the release plan meeting.</div>
<div dir="ltr"> </div>
<div dir="ltr">Currently release plan meeting happens on Thursday 3 PM CST.</div>
<div dir="ltr">Proposal to have test work group meeting is either on Thursday evening 7 or 8 PM CST.</div>
<div dir="ltr"> </div>
<div dir="ltr">Thank you again for all your inputs.</div>
<div dir="ltr"> </div>
<div dir="ltr"> </div>
<div dir="ltr"> </div>
<div dir="ltr"><div class="m_8919110495936005460socmaildefaultfont" dir="ltr" style="font-family:Arial;font-size:10.5pt"><div class="m_8919110495936005460socmaildefaultfont" dir="ltr" style="font-family:Arial;font-size:10.5pt"><div class="m_8919110495936005460socmaildefaultfont" dir="ltr" style="font-family:Arial;font-size:10.5pt"><div class="m_8919110495936005460socmaildefaultfont" dir="ltr" style="font-family:Arial;font-size:10.5pt"><div class="m_8919110495936005460socmaildefaultfont" dir="ltr" style="font-family:Arial;font-size:10.5pt"><div dir="ltr" style="margin-top:20px"><div style="font-size:12pt;font-weight:bold;font-family:sans-serif;color:#7c7c5f">Sivas R. S</div>
<div style="font-size:8pt;font-family:sans-serif;margin-top:10px"><div><span style="font-weight:bold;color:#336699">E-mail: </span><a href="mailto:sivas.srr@in.ibm.com" style="color:#555" target="_blank">sivas.srr@in.ibm.com</a></div>
<div>E2E FSP Test Architecture, OpenBMC Test Lead, Lab Management</div><span class="">
<div>Automation is good, Identifying Defect earlier is better always</div>
<div>9902233500</div>
<div>08046678273</div></span></div></div></div></div></div></div></div></div><div><div class="h5">
<div dir="ltr"> </div>
<div dir="ltr"> </div>
<blockquote dir="ltr" style="border-left:solid #aaaaaa 2px;margin-left:5px;padding-left:5px;direction:ltr;margin-right:0px">----- Original message -----<br>From: Andrew Geissler <<a href="mailto:geissonator@gmail.com" target="_blank">geissonator@gmail.com</a>><br>Sent by: "openbmc" <openbmc-bounces+sivas.srr=<a href="mailto:in.ibm.com@lists.ozlabs.org" target="_blank">in.<wbr>ibm.com@lists.ozlabs.org</a>><br>To: Kurt Taylor <<a href="mailto:kurt.r.taylor@gmail.com" target="_blank">kurt.r.taylor@gmail.com</a>><br>Cc: OpenBMC Maillist <<a href="mailto:openbmc@lists.ozlabs.org" target="_blank">openbmc@lists.ozlabs.org</a>><br>Subject: Re: openbmc test work group - wiki<br>Date: Fri, Jul 20, 2018 11:12 PM<br> <br><tt><font size="3" face="">On Fri, Jul 20, 2018 at 10:58 AM krtaylor <<a href="mailto:kurt.r.taylor@gmail.com" target="_blank">kurt.r.taylor@gmail.com</a>> wrote:</font></tt><br><tt><font size="3" face="">></font></tt><br><tt><font size="3" face="">> On 7/19/18 10:47 PM, Sivas Srr wrote:</font></tt><br><tt><font size="3" face="">></font></tt><br><tt><font size="3" face="">></font></tt><br><tt><font size="3" face="">> Hi All,</font></tt><br><tt><font size="3" face="">></font></tt><br><tt><font size="3" face="">> Have <a href="https://github.com/openbmc/openbmc/wiki/Test-work---group" target="_blank">https://github.com/openbmc/<wbr>openbmc/wiki/Test-work---group</a> created this page in our</font></tt><br><tt><font size="3" face="">> wiki for upcoming test work group. Please review and provide your inputs / raise questions if you need any clarification.</font></tt><br><tt><font size="3" face="">></font></tt><br><tt><font size="3" face="">></font></tt><br><tt><font size="3" face="">> Thanks Sivas! I'll join and help however I can. When would be a good time for a kickoff meeting?</font></tt><br><tt><font size="3" face="">></font></tt><br><tt><font size="3" face="">> It looks like the initial list is a good summary, where do we start, what is the most painful thing to fix? Also, is there room for remote (third-party) CI testing in this WG?</font></tt><br><br><tt><font size="3" face="">Second this one, Brad and I were just chatting a bit on this the other</font></tt><br><tt><font size="3" face="">day, how could we scale the HW CI testing with third parties. Would</font></tt><br><tt><font size="3" face="">def like it if we could discuss within this WG (and any other</font></tt><br><tt><font size="3" face="">improvements to our CI process)</font></tt><br><br><tt><font size="3" face="">></font></tt><br><tt><font size="3" face="">> Kurt Taylor (krtaylor)</font></tt><br><tt><font size="3" face="">></font></tt><br><tt><font size="3" face="">> Sivas R. S</font></tt><br><tt><font size="3" face="">> E-mail: <a href="mailto:sivas.srr@in.ibm.com" target="_blank">sivas.srr@in.ibm.com</a></font></tt><br><tt><font size="3" face="">></font></tt><br><tt><font size="3" face="">> Automation is good, Identifying Defect earlier is better always</font></tt><br><tt><font size="3" face="">> 9902233500</font></tt><br><tt><font size="3" face="">> 08046678273</font></tt><br><tt><font size="3" face="">></font></tt><br><tt><font size="3" face="">></font></tt></blockquote>
<div dir="ltr"> </div></div></div></div><br>
</blockquote></div><br></div>