From: Aaron Conole <aconole@redhat.com>
To: ci@dpdk.org
Subject: [dpdk-ci] May 6, 2021 Community CI Meeting Minutes
Date: Thu, 06 May 2021 19:18:19 -0400 [thread overview]
Message-ID: <f7t5yzva1tw.fsf@redhat.com> (raw)
May 6, 2021
############################################################
Attendees
1. Aaron
2. Brandon Lo
3. David Liu
4. Owen Hilyard
5. David Marchand
6. Ashley Weltz
7. Juraj Linkes
8. Michael Santana
############################################################
Agenda
1. CI Status
2. Test Development
3. Any other business
############################################################
Minutes
============================================================
Performance Percentage Metrics Change
* DTS Merge is blocked by: https://bugs.dpdk.org/show_bug.cgi?id=670
============================================================
CI Status
------------------------------------------------------------
UNH-IOL Community Lab
* Recent failure due to branch pointer being incorrect
* Investigate having a more frequent update interval for infrastructure scripts
* Maybe a routinely scheduled event (“patch tuesday”) could be implemented so that these scripts can be kept up to date
* Brandon will investigate and update the systems to use the correct branches
* ABI test running on all UNH OSes other than Windows
* Unit testing in containers is a work in progress
* Looking to perform internal testing Thursday and Friday / queue that needed to catch up (did over the past weekend)
* Working on reporting failures for when patches fail to apply clean: https://bugs.dpdk.org/show_bug.cgi?id=686
* Have a report for the techboard about static analysis tools (cppcheck, clang), discarded those tools that require build system changes - plan to present to the tech board
* UNH hoping to get more control over the DTS configuration on individual vendor-provided systems, to ease configuration and automation on bare-metal systems
* Start a discussion on the ci mailing list CC-ing the vendors
------------------------------------------------------------
Intel Lab
* No representative today
------------------------------------------------------------
Travis CI / Github Actions / OBS
* Travis - recommending to disable travis monitoring bot
* Useful for individual contributors
* Not as useful for maintainers
* Unusable for the project’s CI infrastructure
* Currently, missing ARM / AARCH64 / 32-bit support in Github Actions
* Need to figure out how to add support for ARM in this area
* ARM also currently working on a community lab for doing the testing
* OBS script work has stalled - looking at transferring that development work to msantana
* Work with Luca B. to get the builds configured
* Need to get the reporting correct
============================================================
Test Development
* DTS Improvement Underway: https://docs.google.com/document/d/1c5S0_mZzFvzZfYkqyORLT2-qNvUb-fBdjA6DGusy4yM/edit#heading=h.crow73oiyskn
* Next Meeting: May 12, 2021
============================================================
Any other business
* Next meeting: May 20, 2021
reply other threads:[~2021-05-06 23:18 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=f7t5yzva1tw.fsf@redhat.com \
--to=aconole@redhat.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).