DPDK CI discussions
 help / color / mirror / Atom feed
From: Patrick MacArthur <pmacarth@iol.unh.edu>
To: ci@dpdk.org
Cc: dpdklab@iol.unh.edu
Subject: [dpdk-ci] agenda items for 2018-05-22 meeting
Date: Mon, 21 May 2018 17:27:50 -0400	[thread overview]
Message-ID: <CABj6NQwN7GNPp24k4uXZ0rGauvfw3xbWhA=pZqLiXXMsP53tQA@mail.gmail.com> (raw)

Hi, all,

I have two items I would like to discuss at tomorrow's meeting:

(1) What to do about patches that have already been applied by the
time the system got to them? My hope is that the system is fast enough
that this should be rare, but there was an issue with upgrading the
Jenkins VM from RHEL 7.4 to RHEL 7.5 that caused the system to fall
behind. For now the system simply ignores patchsets that have already
been applied, but I can change this if the group wants a different
behavior.

(2) I would like to get feedback on the dashboard mockup that I sent on May 10.

Thanks,
Patrick

-- 
Patrick MacArthur
Research and Development, High Performance Networking and Storage
UNH InterOperability Laboratory

                 reply	other threads:[~2018-05-21 21:27 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='CABj6NQwN7GNPp24k4uXZ0rGauvfw3xbWhA=pZqLiXXMsP53tQA@mail.gmail.com' \
    --to=pmacarth@iol.unh.edu \
    --cc=ci@dpdk.org \
    --cc=dpdklab@iol.unh.edu \
    /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).