Re: [RFC PATCH 0/5] replace build code for unit tests

2023-08-09 Thread Patrick Robb
On Wed, Aug 9, 2023 at 11:05 AM Bruce Richardson wrote: > On Wed, Aug 09, 2023 at 10:53:21AM -0400, Patrick Robb wrote: > >It will break our 32 bit arm testing because we are unable to use > meson > >test after building for that SoC, so we run through unit tests with a > >custom list

Re: [RFC PATCH 0/5] replace build code for unit tests

2023-08-09 Thread Bruce Richardson
On Wed, Aug 09, 2023 at 10:53:21AM -0400, Patrick Robb wrote: >It will break our 32 bit arm testing because we are unable to use meson >test after building for that SoC, so we run through unit tests with a >custom list using just dpdk test. It's not a problem, I just need to >know w

Re: [RFC PATCH 0/5] replace build code for unit tests

2023-08-09 Thread Patrick Robb
It will break our 32 bit arm testing because we are unable to use meson test after building for that SoC, so we run through unit tests with a custom list using just dpdk test. It's not a problem, I just need to know when this is going to reach main so I can make the corresponding change to the 32 b

Re: [RFC PATCH 0/5] replace build code for unit tests

2023-08-08 Thread David Marchand
Hello Bruce, On Fri, Jul 21, 2023 at 1:51 PM Bruce Richardson wrote: > > While working on series such as [1] to make DPDK builds more > configurable, the majority of the complexity involved centered on the > unit tests, and ensuring that the individual files were added/removed > from the build as

[RFC PATCH 0/5] replace build code for unit tests

2023-07-21 Thread Bruce Richardson
While working on series such as [1] to make DPDK builds more configurable, the majority of the complexity involved centered on the unit tests, and ensuring that the individual files were added/removed from the build as the components were enabled/disabled. This complexity was exacerbated by: * C f