<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p>Hi Patrick,</p>
    <p>I'm sorry for this serious delay.</p>
    <p>I do believe that retesting is meaningful and Loongson lab should
      support it. Meanwhile, the email based retest framework is
      wonderful and it is not too hard to integrate the retest function
      into the existed dpdk-ci framework. Although I am responsible for
      the Loongson lab, I'm not full-time on it. So, I need some time to
      support the email based retest function in Loongson lab. It may
      take a few weeks. <br>
    </p>
    <div class="moz-cite-prefix">On Thu, Feb 22, 2024 at 1:54PM, Patrick
      Robb wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAJvnSUDreg0ds5aSRa+CKVy5jUCzrBSxCkf9DptXPfWEk-n5rg@mail.gmail.com">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <div dir="ltr">And I forgot to mention, you can set up part of
        this using the dpdk-ci project get_reruns.py script. It polls
        the Rest API for all comment on patch emails events in a given
        timeframe, and uses regex to write a json file containing any
        retest requests from that period. We run this periodically
        (every 15 minutes) at UNH using Jenkins, but I think you could
        do this with a cron job or another solution. 
        <div><br>
        </div>
        <div>Just remember to keep bringing the timeframe parameters
          forward or you will end up consuming a retest request more
          than once! </div>
        <div><br>
        </div>
        <div><a
            href="https://git.dpdk.org/tools/dpdk-ci/tree/tools/get_reruns.py"
            moz-do-not-send="true">https://git.dpdk.org/tools/dpdk-ci/tree/tools/get_reruns.py</a><br>
        </div>
      </div>
    </blockquote>
    <p>Thanks for pointing it out. This script is very useful and it can
      help us more easily support the retest function.</p>
    <p>But, I got an empty output when I tried to get the retest
      requests since 2023-08-01 as following:</p>
    <p># python3 tools/get_reruns.py -ts 2023-08-01 --contexts
"iol-compile-amd64-testing,iol-broadcom-Performance,iol-unit-arm64-testing,github-robot"<br>
      {<br>
          "retests": {},<br>
          "last_comment_timestamp": "2024-02-28T02:27:49.500680"<br>
      }<br>
      Or am I using this script wrong?<br>
    </p>
    <blockquote type="cite"
cite="mid:CAJvnSUDreg0ds5aSRa+CKVy5jUCzrBSxCkf9DptXPfWEk-n5rg@mail.gmail.com"><br>
      <div class="gmail_quote">
        <div dir="ltr" class="gmail_attr">On Thu, Feb 22, 2024 at
          12:55 AM Patrick Robb <<a href="mailto:probb@iol.unh.edu"
            moz-do-not-send="true">probb@iol.unh.edu</a>> 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">
          <div dir="ltr">Hi Zhoumin,
            <div><br>
            </div>
            <div>I wanted to reach out to you about the possibility of
              adding the Loongson lab to the group of labs supporting
              the email based retest framework. Currently, the UNH
              Community Lab and also the GitHub Robot are supporting
              patch retest requests from emails, and we would like to
              extend that to all the publicly reporting CI labs, if
              possible. </div>
            <div><br>
            </div>
            <div>For context, the original announcement:<a
href="https://inbox.dpdk.org/ci/CAC-YWqiXqBYyzPsc4UD7LbUHKha_Vb3=Aot+dQomuRLojy2hvA@mail.gmail.com/"
                target="_blank" moz-do-not-send="true">https://inbox.dpdk.org/ci/CAC-YWqiXqBYyzPsc4UD7LbUHKha_Vb3=Aot+dQomuRLojy2hvA@mail.gmail.com/</a></div>
            <div><br>
            </div>
            <div>Aaron announcing support for the github robot: <a
                href="https://inbox.dpdk.org/ci/f7tedfooq6k.fsf@redhat.com/"
                target="_blank" moz-do-not-send="true">https://inbox.dpdk.org/ci/f7tedfooq6k.fsf@redhat.com/</a></div>
            <div><br>
            </div>
            <div>And the retest framework definition on the <a
                target="_blank"
href="https://mailgw.loongson.cn/linkserver?dest=http%3A%2F%2Fdpdk.org&tid=_____8Bx3+sGUtdlAT8QAA--.41768S3&rcpt=zhoumin@loongson.cn&ifnotice=1&rindex=0"
                moz-do-not-send="true">dpdk.org</a> testing page: <a
                href="https://core.dpdk.org/testing/#requesting-a-patch-retest"
                target="_blank" moz-do-not-send="true">https://core.dpdk.org/testing/#requesting-a-patch-retest</a></div>
            <div><br>
            </div>
            <div>So a format like:</div>
            <div><br>
            </div>
            <div>Recheck-request: iol-compile-amd64-testing,
              iol-broadcom-Performance, iol-unit-arm64-testing,
              github-robot<br>
            </div>
            <div><br>
            </div>
            <div>Is current accepted, and it would be great if we could
              add Loongson support to the list too. What we are
              supporting right now is doing retesting on the original
              DPDK artifact created for a patch when that patch was
              submitted. But we are also thinking of adding in rebasing
              off of tip of branch as a v2 feature. </div>
            <div><br>
            </div>
          </div>
        </blockquote>
      </div>
    </blockquote>
    <p>I think the stateless retesting is more easily to implement the
      retest function. <br>
    </p>
    <p>I wrote a script to report the CI failures from Loongson lab
      three times a day by fetching the test results from
      patches.dpdk.org. This script can help me find the CI failures in
      time. So, sometimes I manually triggered the DPDK CI test in
      Loongson lab as a retest for some patches or series when I found
      there is a test failure caused by Loongson lab self. In this case,
      the retest follows the routines of normal test. So, it will always
      do rebasing before applying the patches or series when do this
      kind of retest. <br>
    </p>
    <p>I think it is simpler for Loongson lab to implement the retest
      function. I think it is also feasible to do the retesting on the
      original DPDK artifact created for a patch when that patch was
      submitted. But, I need some times to reconstruct the existed
      routines. <br>
    </p>
    <p>How do you think of it?</p>
    <p>Best Regards,</p>
    <p>Min Zhou<br>
    </p>
    <blockquote type="cite"
cite="mid:CAJvnSUDreg0ds5aSRa+CKVy5jUCzrBSxCkf9DptXPfWEk-n5rg@mail.gmail.com">
      <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">
          <div dir="ltr">
            <div>Does this sound possible for the Loonson lab? I know
              you are leveraging the dpdk-ci repo for standing up your
              CI testing, but I don't know specifically whether that
              lends itself well towards doing retests later, or if that
              would be a big technical challenge. Let me know! </div>
            <div><br>
            </div>
            <div>If it is possible for the Loongson lab, maybe we can
              discuss in the March 7 CI Testing meeting?</div>
          </div>
        </blockquote>
      </div>
      <br clear="all">
      <div><br>
      </div>
      <span class="gmail_signature_prefix">-- </span><br>
      <div dir="ltr" class="gmail_signature">
        <div dir="ltr">
          <p dir="ltr"
            style="line-height:1.2;margin-top:0pt;margin-bottom:0pt"><font
              face="Arial" color="#000000"><span style="font-size:13.3333px;white-space:pre-wrap">Patrick Robb</span></font></p>
          <p
style="color:rgb(34,34,34);line-height:1.2;margin-top:0pt;margin-bottom:0pt"><span style="font-size:10pt;font-family:Arial;color:rgb(0,0,0);background-color:transparent;vertical-align:baseline;white-space:pre-wrap">Technical Service Manager</span></p>
          <p dir="ltr"
style="color:rgb(34,34,34);line-height:1.2;margin-top:0pt;margin-bottom:0pt"><span style="font-size:10pt;font-family:Arial;color:rgb(0,0,0);background-color:transparent;vertical-align:baseline;white-space:pre-wrap">UNH InterOperability Laboratory</span></p>
          <p dir="ltr"
style="color:rgb(34,34,34);line-height:1.2;margin-top:0pt;margin-bottom:0pt"><span style="font-size:10pt;font-family:Arial;color:rgb(0,0,0);background-color:transparent;vertical-align:baseline;white-space:pre-wrap">21 Madbury Rd, Suite 100, Durham, NH 03824</span></p>
          <p dir="ltr"
style="color:rgb(34,34,34);line-height:1.2;margin-top:0pt;margin-bottom:0pt"><span style="font-size:10pt;font-family:Arial;color:rgb(17,85,204);background-color:transparent;vertical-align:baseline;white-space:pre-wrap"><a style="color:rgb(17,85,204)" target="_blank" href="https://mailgw.loongson.cn/linkserver?dest=http%3A%2F%2Fwww.iol.unh.edu%2F&tid=_____8Bx3+sGUtdlAT8QAA--.41768S3&rcpt=zhoumin@loongson.cn&ifnotice=1&rindex=1" moz-do-not-send="true">www.iol.unh.edu</a></span></p>
          <p dir="ltr"
style="color:rgb(34,34,34);line-height:1.2;margin-top:0pt;margin-bottom:0pt"><br>
          </p>
          <p dir="ltr"
style="color:rgb(34,34,34);line-height:1.2;margin-top:0pt;margin-bottom:0pt"><span style="font-size:10pt;font-family:Arial;color:rgb(51,51,51);background-color:transparent;vertical-align:baseline;white-space:pre-wrap"><img src="https://lh4.googleusercontent.com/7sTY8VswXadak_YT0J13osh5ockNVRX2BuYaRsKoTTpkpilBokA0WlocYHLB4q7XUgXNHka6-ns47S8R_am0sOt7MYQQ1ILQ3S-P5aezsrjp3-IsJMmMrErHWmTARNgZhpAx06n2" style="border: none;" moz-do-not-send="true" width="150" height="37"></span></p>
        </div>
      </div>
    </blockquote>
  </body>
</html>