DPDK CI discussions
 help / color / mirror / Atom feed
From: Lincoln Lavoie <lylavoie@iol.unh.edu>
To: Ali Alnubani <alialnu@nvidia.com>
Cc: "ci@dpdk.org" <ci@dpdk.org>
Subject: Re: [dpdk-ci] August 12 Community CI Minutes
Date: Thu, 12 Aug 2021 11:04:28 -0400	[thread overview]
Message-ID: <CAOE1vsOv1XJA5nbAbT3=aviUE5VU7QhRKuuGyvH=LO+1bepBeA@mail.gmail.com> (raw)
In-Reply-To: <DM4PR12MB5167A98282B3F3815F719CC3DAF99@DM4PR12MB5167.namprd12.prod.outlook.com>

[-- Attachment #1: Type: text/plain, Size: 5316 bytes --]

For the MLX system, I think that should be ok.  Owen ran into some issues
on the other systems when we tried to upgrade to 90, and rolled back to 87
for the time being.  Ideally, we're still aiming to get everyone to a
common ground, so we're not having to maintain configurations for multiple
versions of DTS and TRex.

Cheers,
Lincoln

On Thu, Aug 12, 2021 at 10:47 AM Ali Alnubani <alialnu@nvidia.com> wrote:

> > * Work is being done on bringing updating trex from 87 to 90.
>
>
>
> Can we move to latest (v2.91) instead? It resolves this issue in mlx5:
>
> https://github.com/cisco-system-traffic-generator/trex-core/issues/678.
>
>
>
> Thanks,
> Ali
>
>
>
> *From:* ci <ci-bounces@dpdk.org> *On Behalf Of *Lincoln Lavoie
> *Sent:* Thursday, August 12, 2021 5:41 PM
> *To:* ci@dpdk.org
> *Subject:* [dpdk-ci] August 12 Community CI Minutes
>
>
>
> DPDK Community CI Meeting Minutes
>
> August 12, 2021
>
> #####################################################################
> Attendees
>
> 1. Lincoln Lavoie
> 2. Owen Hilyard
> 3. Brandon Lo
> 4. Aaron Conole
> 5. Michael Santana
> 6. Ali Alnubani
> 7. Henry Nadeau
> 8. Lijuan Tu
> 9. Juraj Linkes
>
> #####################################################################
> Agenda
>
> 1. CI Status
> 2. Test Development
> 3. Any other business
>
> #####################################################################
> Minutes
>
> =====================================================================
> CI Status
>
> ---------------------------------------------------------------------
> UNH-IOL Community Lab
> * Alpine linux fails to build performance-thread example
>    * Bugzilla https://bugs.dpdk.org/show_bug.cgi?id=756
> * FreeBSD 13 unit test failures
>    * Bugzilla https://bugs.dpdk.org/show_bug.cgi?id=761
> * Intel 40G machine is back online
> * Reached out to Broadcom for support with ARM machine
> * Email split is in effect for patchworks
>    * Unit and compile tests are now split up by architecture
> * ABI references are now rebuilt and comparing against v21.08
> * Work is being done on bringing updating trex from 87 to 90.
> * Continued work on fixing functional tests where changes in DTS caused
> breakages.
> * Spell check patch (corrections to documentation) got merged, working on
> a back port patch as well.  Couple of new spelling errors were merged,
> Henry is working on a patch for those as well.
> * UNH will look into changing the email reporting on failures, per
> https://bugs.dpdk.org/show_bug.cgi?id=716
>
> ---------------------------------------------------------------------
> Intel Lab
>
> * A request for changes to the email reporting should be in place now,
> with patch submitters also emailed directly on failures.
> * Fixed some issues with the lab systems.
> * Working on DTS CI, waiting on dts-test-report email list to be
> integrated into patchwork, sending to the test-report email list in the
> meantime.
> * Owen provided a script to identify which tests should be run, based on
> the changes in the patch; this could be used to improve the coverage of the
> DTS CI testing. Owen will send a docker file to create an image that can
> run the script.
> * DTS CI is going to be offline for a few days, while doing dry-runs of
> testing.
>
> ---------------------------------------------------------------------
> Github Actions & OBS
>
> * Added support for mutli-workflow actions, which will be used when adding
> additional runners.
> * Patch series has been submitted for the work to enable OBS. Aaron is
> sending some comments, and there will be a request for Juraj to review.
>
> =====================================================================
> Test Development
>
> * Aaron still needs to work on the func_reentrancy_autotest to improve the
> debugging support.
> * DTS Improvements
>    * Discussions are progressing. Work is being tracked here:
> https://docs.google.com/document/d/1c5S0_mZzFvzZfYkqyORLT2-qNvUb-fBdjA6DGusy4yM/edit
>    * Next Meeting: August 4, 2021
>    * Group got through all the feedback in the document.
>    * Starting to get work in place to clean up the python code
> (auto-formatting), and linting.  Aiming to fully deploy this after the
> 21.11 release.
>    * Aiming to ensure a subset of DTS test cases used on the DPDK CI have
> CI testing enabled within DTS.
>
> =====================================================================
> Any other business
>
> * Next Meeting: August 26, 2021
> * New arm hardware potentially available to add to the UNH lab.  Need to
> confirm a plan for the traffic generator for the lab (spare server or using
> the existing arm TG server for both arm systems). Lincoln to follow up to
> Juraj on the current TG specs.
>
>
>
> --
>
> *Lincoln Lavoie*
>
> Principal 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/>
>


-- 
*Lincoln Lavoie*
Principal 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: 9041 bytes --]

  reply	other threads:[~2021-08-12 15:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-12 14:40 Lincoln Lavoie
2021-08-12 14:47 ` Ali Alnubani
2021-08-12 15:04   ` Lincoln Lavoie [this message]
2021-08-13  6:07 ` Thomas Monjalon
2021-08-13 12:20   ` Lincoln Lavoie
2021-08-13 13:20     ` Thomas Monjalon
2021-08-13 16:21       ` Brandon Lo

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='CAOE1vsOv1XJA5nbAbT3=aviUE5VU7QhRKuuGyvH=LO+1bepBeA@mail.gmail.com' \
    --to=lylavoie@iol.unh.edu \
    --cc=alialnu@nvidia.com \
    --cc=ci@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).