From: "Richardson, Bruce" <bruce.richardson@intel.com>
To: Brandon Lo <blo@iol.unh.edu>
Cc: Thomas Monjalon <thomas@monjalon.net>,
"ci@dpdk.org" <ci@dpdk.org>, dpdklab <dpdklab@iol.unh.edu>
Subject: Re: [dpdk-ci] FreeBSD 13 Unit Testing -- Two Tests Failing
Date: Fri, 16 Jul 2021 16:21:54 +0000 [thread overview]
Message-ID: <2ea1186a1ead49f7a7228f1f48b79662@intel.com> (raw)
In-Reply-To: <CAOeXdvYZvOez7ki0p79ES7q5r8=KTWyiPDr66uEstGehf9gD=w@mail.gmail.com>
> -----Original Message-----
> From: Brandon Lo <blo@iol.unh.edu>
> Sent: Friday, July 16, 2021 5:19 PM
> To: Richardson, Bruce <bruce.richardson@intel.com>
> Cc: Thomas Monjalon <thomas@monjalon.net>; ci@dpdk.org; dpdklab
> <dpdklab@iol.unh.edu>
> Subject: Re: [dpdk-ci] FreeBSD 13 Unit Testing -- Two Tests Failing
>
> On Wed, Jul 14, 2021 at 8:01 AM Richardson, Bruce
> <bruce.richardson@intel.com> wrote:
> >
> > I don't believe we have interrupt support on FreeBSD, so it should
> probably return with TEST_SKIPPED immediately. As for the other, I'd have
> to investigate.
> > I'll try and test both this afternoon and see if I can see any quick
> fixes.
> >
> > /Bruce
>
> Hi Bruce,
>
> Thank you for looking into this.
> Were you able to reproduce the issues on your end?
>
Yes, I was able to reproduce the issues, but haven't been able to dig into them yet. Both tests should be passing on FreeBSD, though, since it appears interrupt support is present.
next prev parent reply other threads:[~2021-07-16 16:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-13 20:55 Brandon Lo
2021-07-14 11:37 ` Thomas Monjalon
2021-07-14 12:01 ` Richardson, Bruce
2021-07-16 16:18 ` Brandon Lo
2021-07-16 16:21 ` Richardson, Bruce [this message]
2021-08-11 21:00 ` Brandon Lo
2021-09-17 15:11 ` Richardson, Bruce
2021-10-02 14:43 ` David Marchand
2021-10-04 7:46 ` Richardson, Bruce
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=2ea1186a1ead49f7a7228f1f48b79662@intel.com \
--to=bruce.richardson@intel.com \
--cc=blo@iol.unh.edu \
--cc=ci@dpdk.org \
--cc=dpdklab@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).