From: Lincoln Lavoie <lylavoie@iol.unh.edu>
To: dev@dpdk.org, ci@dpdk.org
Subject: [dpdk-ci] CI results reporting
Date: Tue, 30 Jun 2020 16:35:09 -0400 [thread overview]
Message-ID: <CAOE1vsPwOWRaUxOJnAUZmZrSK1TwJu+zPJRD+7Y2KC_CwrZ+4w@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 571 bytes --]
Hello All,
One topic that came up during today's meeting was the results reporting
strategy in patch sets, which is currently different between labs. We
wanted to get some input from the community before pushing for alignment
between the labs, etc. To help track things, let's keep the discussion on
the bug here: https://bugs.dpdk.org/show_bug.cgi?id=497
Cheers,
Lincoln
--
*Lincoln Lavoie*
Senior Engineer, Broadband Technologies
21 Madbury Rd., Ste. 100, Durham, NH 03824
lylavoie@iol.unh.edu
https://www.iol.unh.edu
+1-603-674-2755 (m)
<https://www.iol.unh.edu/>
[-- Attachment #2: Type: text/html, Size: 1605 bytes --]
reply other threads:[~2020-06-30 20:35 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=CAOE1vsPwOWRaUxOJnAUZmZrSK1TwJu+zPJRD+7Y2KC_CwrZ+4w@mail.gmail.com \
--to=lylavoie@iol.unh.edu \
--cc=ci@dpdk.org \
--cc=dev@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).