DPDK CI discussions
 help / color / mirror / Atom feed
From: Patrick MacArthur <pmacarth@iol.unh.edu>
To: ci@dpdk.org, Bob Noseworthy <ren@iol.unh.edu>
Cc: dpdklab@iol.unh.edu
Subject: [dpdk-ci] meeting topics
Date: Tue, 24 Apr 2018 00:56:12 -0400	[thread overview]
Message-ID: <CABj6NQxM16pGV_uVJbh20VsgQmRcB2FqfhtHiiEoN8XkPMd-+w@mail.gmail.com> (raw)

Hi, all,

Here are a few things I would like to discuss on today's DPDK lab call:

- What to do about patch apply failures and build errors?
- How to deal with new package dependencies introduced by a patch?
(e.g., a recent patch introduced a dependency on libedit)
- How long to keep generated tarballs and log files for? For
reference, at the moment the generated tarballs appear to be taking
the most disk space. The ideal might be to set up the tarballs in a
way where they can be 100% reproducible in which case we don't need to
store them after the performance logs are generated since we can
regenerate it from the git commit hash and patchset from patchwork.

Thanks,
Patrick

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

                 reply	other threads:[~2018-04-24  4:56 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=CABj6NQxM16pGV_uVJbh20VsgQmRcB2FqfhtHiiEoN8XkPMd-+w@mail.gmail.com \
    --to=pmacarth@iol.unh.edu \
    --cc=ci@dpdk.org \
    --cc=dpdklab@iol.unh.edu \
    --cc=ren@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).