From: "Mcnamara, John" <john.mcnamara@intel.com>
To: Patrick Robb <probb@iol.unh.edu>
Cc: "ci@dpdk.org" <ci@dpdk.org>, Adam Hassick <ahassick@iol.unh.edu>
Subject: RE: DPDK Coverity test run
Date: Thu, 16 Nov 2023 20:56:35 +0000 [thread overview]
Message-ID: <PH8PR11MB6804671B53A4138C09DF99A3FCB0A@PH8PR11MB6804.namprd11.prod.outlook.com> (raw)
In-Reply-To: <CAJvnSUDZWWAbVcmYcbH6JoV3_yqFTqpwirJLgOpguskzMCdD2w@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1061 bytes --]
My bad Patrick. You are right. Thanks.
From: Patrick Robb <probb@iol.unh.edu>
Sent: Thursday, November 16, 2023 8:44 PM
To: Mcnamara, John <john.mcnamara@intel.com>
Cc: ci@dpdk.org; Adam Hassick <ahassick@iol.unh.edu>
Subject: Re: DPDK Coverity test run
Hi John,
I am seeing a Nov 15 run here: https://scan.coverity.com/projects/dpdk-data-plane-development-kit
Let me know if that isn't right. Thanks.
Patrick
On Thu, Nov 16, 2023 at 3:38 PM Mcnamara, John <john.mcnamara@intel.com<mailto:john.mcnamara@intel.com>> wrote:
Hi Folks,
AFAIK the DPDK Coverity tests run on Monday, Wednesday and Friday. I didn’t see a run on Wednesday. Is that because Monday’s run had already captured RC3 and there weren’t any additional changes to run on Wednesday? Or did it fail to run on Wednesday for some reason?
John
--
Patrick Robb
Technical Service Manager
UNH InterOperability Laboratory
21 Madbury Rd, Suite 100, Durham, NH 03824
www.iol.unh.edu<http://www.iol.unh.edu/>
[Image removed by sender.]
[-- Attachment #1.2: Type: text/html, Size: 6962 bytes --]
[-- Attachment #2: ~WRD0000.jpg --]
[-- Type: image/jpeg, Size: 823 bytes --]
next prev parent reply other threads:[~2023-11-16 20:56 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAC-YWqiQfH4Rx-Et1jGHhGK9i47d0AArKy-B2P77iYbbM+Lpig@mail.gmail.com>
[not found] ` <C3B08390-DA6D-4BDC-BBD7-98561F92FE33@oktetlabs.ru>
[not found] ` <35340484-1d7e-7e5f-cad4-c965ba541397@oktetlabs.ru>
2023-08-17 17:03 ` Setting up DPDK PMD Test Suite Adam Hassick
2023-08-18 18:40 ` Andrew Rybchenko
2023-08-20 8:40 ` Andrew Rybchenko
2023-08-21 14:19 ` Adam Hassick
2023-08-23 14:45 ` Adam Hassick
2023-08-24 8:22 ` Andrew Rybchenko
2023-08-24 14:30 ` Adam Hassick
2023-08-24 18:34 ` Andrew Rybchenko
2023-08-24 20:29 ` Adam Hassick
2023-08-24 20:54 ` Andrew Rybchenko
2023-08-25 13:57 ` Andrew Rybchenko
2023-08-25 14:06 ` Adam Hassick
2023-08-25 14:41 ` Andrew Rybchenko
2023-08-25 17:35 ` Andrew Rybchenko
2023-08-28 15:02 ` Adam Hassick
2023-08-28 21:05 ` Andrew Rybchenko
2023-08-29 12:07 ` Andrew Rybchenko
2023-08-29 14:02 ` Adam Hassick
2023-08-29 20:43 ` Andrew Rybchenko
2023-08-31 19:38 ` Adam Hassick
2023-09-01 7:59 ` Andrew Rybchenko
2023-09-05 15:01 ` Adam Hassick
2023-09-06 11:36 ` Andrew Rybchenko
2023-09-06 15:00 ` Adam Hassick
2023-09-08 14:57 ` Adam Hassick
2023-09-13 15:45 ` Andrew Rybchenko
2023-09-18 6:15 ` Andrew Rybchenko
2023-09-18 6:23 ` Konstantin Ushakov
2023-09-18 6:26 ` Andrew Rybchenko
2023-09-18 14:44 ` Adam Hassick
2023-09-18 15:04 ` Andrew Rybchenko
2023-10-04 13:48 ` Adam Hassick
2023-10-05 10:25 ` Andrew Rybchenko
2023-10-10 14:09 ` Adam Hassick
2023-10-11 11:46 ` Andrew Rybchenko
2023-10-23 11:11 ` Andrew Rybchenko
2023-10-25 20:27 ` Adam Hassick
2023-10-26 12:19 ` Andrew Rybchenko
2023-10-26 17:44 ` Adam Hassick
2023-10-27 8:01 ` Andrew Rybchenko
2023-10-27 19:13 ` Andrew Rybchenko
2023-11-06 23:16 ` Adam Hassick
2023-11-07 16:57 ` Andrew Rybchenko
2023-11-07 20:30 ` Adam Hassick
2023-11-08 7:20 ` Andrew Rybchenko
2023-11-16 20:03 ` Adam Hassick
2023-11-16 20:38 ` DPDK Coverity test run Mcnamara, John
2023-11-16 20:43 ` Patrick Robb
2023-11-16 20:56 ` Mcnamara, John [this message]
2023-11-20 17:18 ` Setting up DPDK PMD Test Suite Andrew Rybchenko
2023-12-01 14:39 ` Andrew Rybchenko
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=PH8PR11MB6804671B53A4138C09DF99A3FCB0A@PH8PR11MB6804.namprd11.prod.outlook.com \
--to=john.mcnamara@intel.com \
--cc=ahassick@iol.unh.edu \
--cc=ci@dpdk.org \
--cc=probb@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).