* [dpdk-ci] meeting topics
@ 2018-04-24 4:56 Patrick MacArthur
0 siblings, 0 replies; only message in thread
From: Patrick MacArthur @ 2018-04-24 4:56 UTC (permalink / raw)
To: ci, Bob Noseworthy; +Cc: dpdklab
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.
Research and Development, High Performance Networking and Storage
UNH InterOperability Laboratory
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2018-04-24 4:56 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-04-24 4:56 [dpdk-ci] meeting topics Patrick MacArthur
DPDK CI discussions
This inbox may be cloned and mirrored by anyone:
git clone --mirror http://inbox.dpdk.org/ci/0 ci/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 ci ci/ http://inbox.dpdk.org/ci \
Example config snippet for mirrors.
Newsgroup available over NNTP:
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git