DPDK CI discussions
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: ci@dpdk.org
Subject: [dpdk-ci] [Bug 497] Reporting format per patchset
Date: Tue, 30 Jun 2020 20:30:42 +0000	[thread overview]
Message-ID: <bug-497-149@http.bugs.dpdk.org/> (raw)

https://bugs.dpdk.org/show_bug.cgi?id=497

            Bug ID: 497
           Summary: Reporting format per patchset
           Product: lab
           Version: unspecified
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: job scripts
          Assignee: ci@dpdk.org
          Reporter: lylavoie@iol.unh.edu
                CC: dpdklab@iol.unh.edu
  Target Milestone: ---

Currently Intel lab reports the same results back to each individual patch in
the set, UNH lab reports back to the first patch in the set. To assist the
developers, it would be good to standardize on the reporting approach over all,
labs.

Options are:
1. results sent to all patches in set
2. results sent to first patch in set
3. results sent to last patch in set
4. other

-- 
You are receiving this mail because:
You are the assignee for the bug.

                 reply	other threads:[~2020-06-30 20:30 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-497-149@http.bugs.dpdk.org/ \
    --to=bugzilla@dpdk.org \
    --cc=ci@dpdk.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).