DPDK CI discussions
 help / color / mirror / Atom feed
From: Brandon Lo <blo@iol.unh.edu>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: Lincoln Lavoie <lylavoie@iol.unh.edu>, ci@dpdk.org
Subject: Re: [dpdk-ci] Community CI Meeting Minutes - July 29, 2021
Date: Thu, 29 Jul 2021 14:55:03 -0400	[thread overview]
Message-ID: <CAOeXdvYbvdw+Rq+YoKOTZyokAtfq1wZ5ygo6pmfwzwN+jpMZtA@mail.gmail.com> (raw)
In-Reply-To: <2177893.HOMrD9adHb@thomas>

On Thu, Jul 29, 2021 at 11:16 AM Thomas Monjalon <thomas@monjalon.net> wrote:
> Please propose the exact split with test report names,
> so we can evaluate if the split is convenient,
> and check if it is not too much split.

Hi Thomas,

We were planning on splitting the iol-testing label into four labels:
iol-x86_64-compile-testing
iol-x86_64-unit-testing
iol-aarch64-compile-testing
iol-aarch64-unit-testing

This change would separate jobs into labels based on the job name.
dpdk_meson_compile, dpdk_compile_spdk, mingw64_compile jobs in compile testing,
dpdk_unit_test, spdk_unit_test in unit testing.

The architectures will be categorized by target instead of host machine.

If you have any suggestions to get a more convenient split, please let us know.

Thanks,
Brandon




--
Brandon Lo
UNH InterOperability Laboratory
21 Madbury Rd, Suite 100, Durham, NH 03824
blo@iol.unh.edu
www.iol.unh.edu

  reply	other threads:[~2021-07-29 18:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-29 14:45 Lincoln Lavoie
2021-07-29 15:17 ` Thomas Monjalon
2021-07-29 18:55   ` Brandon Lo [this message]
2021-07-30  6:36     ` Thomas Monjalon

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=CAOeXdvYbvdw+Rq+YoKOTZyokAtfq1wZ5ygo6pmfwzwN+jpMZtA@mail.gmail.com \
    --to=blo@iol.unh.edu \
    --cc=ci@dpdk.org \
    --cc=lylavoie@iol.unh.edu \
    --cc=thomas@monjalon.net \
    /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).