From: Patrick Robb <probb@iol.unh.edu>
To: "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>
Cc: Aaron Conole <aconole@redhat.com>,
Ferruh Yigit <ferruh.yigit@amd.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"stable@dpdk.org" <stable@dpdk.org>,
"Marchand, David" <david.marchand@redhat.com>,
"Richardson, Bruce" <bruce.richardson@intel.com>
Subject: Re: [PATCH V2] examples/pipeline: fix include path for rte_log.h
Date: Tue, 16 Jul 2024 12:33:39 -0400 [thread overview]
Message-ID: <CAJvnSUCaTSv7L==_JWkqors3VVV4UfacT5GnynyvPx7hO6s5fQ@mail.gmail.com> (raw)
In-Reply-To: <CAJvnSUA7x7EN4c6CfKQq5m2XKpPXZT3ksK0-3-ED+2WEJJodzQ@mail.gmail.com>
On Wed, Feb 14, 2024 at 3:17 PM Patrick Robb <probb@iol.unh.edu> wrote:
>
>
>
> On Wed, Feb 14, 2024 at 3:00 PM Dumitrescu, Cristian <cristian.dumitrescu@intel.com> wrote:
>>
>>
>>
>> [Cristian]
>> Yes, you are right, we do have a DTS test suite for the pipeline library.
>>
>> It would be great to run it automatically as part of the CI testing. Just a word of caution though: I am not the owner of those tests, and also not intimately familiar with them, so it might be hard to find volunteers to setup the test suite, that the only problem that I see unfortunately. But we should try and see if there are any issues at all.
>>
>> Thanks,
>> Cristian
>
>
> Okay, the setup doesn't look too burdensome anyhow so we should be alright with just the team here at UNH. I'll let you know how it goes.
Sorry I realized today I never provided an update here. Back in
February I did wire a testbed according to the testplan, insalled the
dependencies and gave it a run, which was not passing.
It would have been possible to pick apart the testsuite, manually
running the example app to see whether the issue laid in the testbed
setup, testsuite implementation, or somewhere else. But, it would have
taken time and the premise of this effort was that it would be a quick
setup, so I gave up as our efforts should go towards making additions
to new DTS now, instead of debugging old DTS.
I'm sorry that there isn't pipeline coverage in CI currently though -
something to target going forward.
next prev parent reply other threads:[~2024-07-16 16:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-13 14:52 [PATCH] " Cristian Dumitrescu
2024-02-13 16:18 ` David Marchand
2024-02-13 17:22 ` Dumitrescu, Cristian
2024-02-13 17:38 ` [PATCH V2] " Cristian Dumitrescu
2024-02-14 11:22 ` Ferruh Yigit
2024-02-14 16:25 ` Aaron Conole
2024-02-14 19:32 ` Patrick Robb
2024-02-14 20:00 ` Dumitrescu, Cristian
2024-02-14 20:17 ` Patrick Robb
2024-07-16 16:33 ` Patrick Robb [this message]
2024-07-17 10:10 ` Ferruh Yigit
2024-02-14 17:22 ` Dumitrescu, Cristian
2024-02-15 12:17 ` Ferruh Yigit
2024-02-15 13:32 ` Ferruh Yigit
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='CAJvnSUCaTSv7L==_JWkqors3VVV4UfacT5GnynyvPx7hO6s5fQ@mail.gmail.com' \
--to=probb@iol.unh.edu \
--cc=aconole@redhat.com \
--cc=bruce.richardson@intel.com \
--cc=cristian.dumitrescu@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.com \
--cc=stable@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).