[dpdk-ci] FreeBSD 13 Unit Testing -- Two Tests Failing

[dpdk-ci] FreeBSD 13 Unit Testing -- Two Tests Failing

[Brandon Lo]

Hello all,

I am looking to expand the coverage of the community lab by running
DPDK unit tests on FreeBSD 13.
Currently, in the fast tests suite, there are 2 tests failing and
preventing the environment from being put into production:
interrupt_autotest and memory_autotest.
This test was on DPDK main, commit a95bbb72623c310df4d0c8ad45c2ee06f538e01b.

interrupt_autotest fails quite quickly:
stdout:
RTE>>interrupt_autotest
Check unknown valid interrupt full path
callback has not been called
failure occurred during checking unknown valid interrupt full path
Clearing for interrupt tests
Test Failed

memory_autotest fails after dumping memory:
stdout:
RTE>>memory_autotest
Dump memory layout
...
Error getting segment fd's
Test Failed

Could somebody more familiar with the tests confirm if these are real issues?

Thanks,
Brandon

--
Brandon Lo

UNH InterOperability Laboratory

21 Madbury Rd, Suite 100, Durham, NH 03824

blo@iol.unh.edu

www.iol.unh.edu

Re: [dpdk-ci] FreeBSD 13 Unit Testing -- Two Tests Failing

[Thomas Monjalon]

+Cc Bruce, maintainer of the FreeBSD port

13/07/2021 22:55, Brandon Lo:
> Hello all,
> 
> I am looking to expand the coverage of the community lab by running
> DPDK unit tests on FreeBSD 13.
> Currently, in the fast tests suite, there are 2 tests failing and
> preventing the environment from being put into production:
> interrupt_autotest and memory_autotest.
> This test was on DPDK main, commit a95bbb72623c310df4d0c8ad45c2ee06f538e01b.
> 
> interrupt_autotest fails quite quickly:
> stdout:
> RTE>>interrupt_autotest
> Check unknown valid interrupt full path
> callback has not been called
> failure occurred during checking unknown valid interrupt full path
> Clearing for interrupt tests
> Test Failed
> 
> memory_autotest fails after dumping memory:
> stdout:
> RTE>>memory_autotest
> Dump memory layout
> ...
> Error getting segment fd's
> Test Failed
> 
> Could somebody more familiar with the tests confirm if these are real issues?
> 
> Thanks,
> Brandon
> 
> --
> Brandon Lo
> 
> UNH InterOperability Laboratory
> 
> 21 Madbury Rd, Suite 100, Durham, NH 03824
> 
> blo@iol.unh.edu
> 
> www.iol.unh.edu
> 

Re: [dpdk-ci] FreeBSD 13 Unit Testing -- Two Tests Failing

[Richardson, Bruce]

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

> -----Original Message-----
> From: Thomas Monjalon <thomas@monjalon.net>
> Sent: Wednesday, July 14, 2021 12:38 PM
> To: Brandon Lo <blo@iol.unh.edu>
> Cc: ci@dpdk.org; dpdklab <dpdklab@iol.unh.edu>; Richardson, Bruce
> <bruce.richardson@intel.com>
> Subject: Re: [dpdk-ci] FreeBSD 13 Unit Testing -- Two Tests Failing
> 
> +Cc Bruce, maintainer of the FreeBSD port
> 
> 13/07/2021 22:55, Brandon Lo:
> > Hello all,
> >
> > I am looking to expand the coverage of the community lab by running
> > DPDK unit tests on FreeBSD 13.
> > Currently, in the fast tests suite, there are 2 tests failing and
> > preventing the environment from being put into production:
> > interrupt_autotest and memory_autotest.
> > This test was on DPDK main, commit
> a95bbb72623c310df4d0c8ad45c2ee06f538e01b.
> >
> > interrupt_autotest fails quite quickly:
> > stdout:
> > RTE>>interrupt_autotest
> > Check unknown valid interrupt full path
> > callback has not been called
> > failure occurred during checking unknown valid interrupt full path
> > Clearing for interrupt tests
> > Test Failed
> >
> > memory_autotest fails after dumping memory:
> > stdout:
> > RTE>>memory_autotest
> > Dump memory layout
> > ...
> > Error getting segment fd's
> > Test Failed
> >
> > Could somebody more familiar with the tests confirm if these are real
> issues?
> >
> > Thanks,
> > Brandon
> >
> > --
> > Brandon Lo
> >
> > UNH InterOperability Laboratory
> >
> > 21 Madbury Rd, Suite 100, Durham, NH 03824
> >
> > blo@iol.unh.edu
> >
> > www.iol.unh.edu
> >
> 
> 
> 
> 

Re: [dpdk-ci] FreeBSD 13 Unit Testing -- Two Tests Failing

[Brandon Lo]

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?

Regards,
Brandon

--
Brandon Lo
UNH InterOperability Laboratory
21 Madbury Rd, Suite 100, Durham, NH 03824
blo@iol.unh.edu
www.iol.unh.edu

Re: [dpdk-ci] FreeBSD 13 Unit Testing -- Two Tests Failing

[Richardson, Bruce]

> -----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.

Re: [dpdk-ci] FreeBSD 13 Unit Testing -- Two Tests Failing

[Brandon Lo]

On Fri, Jul 16, 2021 at 12:21 PM Richardson, Bruce
<bruce.richardson@intel.com> wrote:
> 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.

Hi Bruce,

We have created a new bug ticket in Bugzilla to keep track of this
item: https://bugs.dpdk.org/show_bug.cgi?id=761.
Please update the status there if you get a chance.

Thanks,
Brandon



-- 
Brandon Lo
UNH InterOperability Laboratory
21 Madbury Rd, Suite 100, Durham, NH 03824
blo@iol.unh.edu
www.iol.unh.edu

Re: [dpdk-ci] FreeBSD 13 Unit Testing -- Two Tests Failing

[Richardson, Bruce]

> -----Original Message-----
> From: Thomas Monjalon <thomas@monjalon.net>
> Sent: Wednesday, July 14, 2021 12:38 PM
> To: Brandon Lo <blo@iol.unh.edu>
> Cc: ci@dpdk.org; dpdklab <dpdklab@iol.unh.edu>; Richardson, Bruce
> <bruce.richardson@intel.com>
> Subject: Re: [dpdk-ci] FreeBSD 13 Unit Testing -- Two Tests Failing
> 
> +Cc Bruce, maintainer of the FreeBSD port
> 

Patch for memory autotest submitted to dev list:
http://patches.dpdk.org/project/dpdk/patch/20210917150917.90892-1-bruce.richardson@intel.com/

> 13/07/2021 22:55, Brandon Lo:
> > Hello all,
> >
> > I am looking to expand the coverage of the community lab by running
> > DPDK unit tests on FreeBSD 13.
> > Currently, in the fast tests suite, there are 2 tests failing and
> > preventing the environment from being put into production:
> > interrupt_autotest and memory_autotest.
> > This test was on DPDK main, commit
> a95bbb72623c310df4d0c8ad45c2ee06f538e01b.
> >
> > interrupt_autotest fails quite quickly:
> > stdout:
> > RTE>>interrupt_autotest
> > Check unknown valid interrupt full path
> > callback has not been called
> > failure occurred during checking unknown valid interrupt full path
> > Clearing for interrupt tests
> > Test Failed
> >
> > memory_autotest fails after dumping memory:
> > stdout:
> > RTE>>memory_autotest
> > Dump memory layout
> > ...
> > Error getting segment fd's
> > Test Failed
> >
> > Could somebody more familiar with the tests confirm if these are real
> issues?
> >
> > Thanks,
> > Brandon
> >
> > --
> > Brandon Lo
> >
> > UNH InterOperability Laboratory
> >
> > 21 Madbury Rd, Suite 100, Durham, NH 03824
> >
> > blo@iol.unh.edu
> >
> > www.iol.unh.edu
> >
> 
> 
> 
> 

Re: [dpdk-ci] FreeBSD 13 Unit Testing -- Two Tests Failing

[David Marchand]

On Fri, Sep 17, 2021 at 5:11 PM Richardson, Bruce
<bruce.richardson@intel.com> wrote:
> > -----Original Message-----
> > From: Thomas Monjalon <thomas@monjalon.net>
> > Sent: Wednesday, July 14, 2021 12:38 PM
> > To: Brandon Lo <blo@iol.unh.edu>
> > Cc: ci@dpdk.org; dpdklab <dpdklab@iol.unh.edu>; Richardson, Bruce
> > <bruce.richardson@intel.com>
> > Subject: Re: [dpdk-ci] FreeBSD 13 Unit Testing -- Two Tests Failing
> >
> > +Cc Bruce, maintainer of the FreeBSD port
> >
>
> Patch for memory autotest submitted to dev list:
> http://patches.dpdk.org/project/dpdk/patch/20210917150917.90892-1-bruce.richardson@intel.com/

Merged in main.
Thanks.

-- 
David Marchand

Re: [dpdk-ci] FreeBSD 13 Unit Testing -- Two Tests Failing

[Richardson, Bruce]

> -----Original Message-----
> From: David Marchand <david.marchand@redhat.com>
> Sent: Saturday, October 2, 2021 3:44 PM
> To: Richardson, Bruce <bruce.richardson@intel.com>; dpdklab
> <dpdklab@iol.unh.edu>
> Cc: Thomas Monjalon <thomas@monjalon.net>; Brandon Lo <blo@iol.unh.edu>;
> ci@dpdk.org
> Subject: Re: [dpdk-ci] FreeBSD 13 Unit Testing -- Two Tests Failing
> 
> On Fri, Sep 17, 2021 at 5:11 PM Richardson, Bruce
> <bruce.richardson@intel.com> wrote:
> > > -----Original Message-----
> > > From: Thomas Monjalon <thomas@monjalon.net>
> > > Sent: Wednesday, July 14, 2021 12:38 PM
> > > To: Brandon Lo <blo@iol.unh.edu>
> > > Cc: ci@dpdk.org; dpdklab <dpdklab@iol.unh.edu>; Richardson, Bruce
> > > <bruce.richardson@intel.com>
> > > Subject: Re: [dpdk-ci] FreeBSD 13 Unit Testing -- Two Tests Failing
> > >
> > > +Cc Bruce, maintainer of the FreeBSD port
> > >
> >
> > Patch for memory autotest submitted to dev list:
> > http://patches.dpdk.org/project/dpdk/patch/20210917150917.90892-1-
> bruce.richardson@intel.com/
> 
> Merged in main.
> Thanks.
> 
> --
> David Marchand

Thanks David.

The interrupt test is the other one called out here, and I believe that to be more complex. I'm not confident about having time to fix it myself.

Regards,
/Bruce