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 bit unit testing script beforehand.
- [RFC PATCH 0/5] replace build code for unit tests Bruce Richardson
- [RFC PATCH 1/5] app/test: add new macros for various... Bruce Richardson
- [RFC PATCH 2/5] app/test: tag tests with the test ty... Bruce Richardson
- [RFC PATCH 3/5] app/test: build using per-file depen... Bruce Richardson
- [RFC PATCH 4/5] app/test: define unit tests suites b... Bruce Richardson
- [RFC PATCH 5/5] app/test: add fast test suite to new... Bruce Richardson
- Re: [RFC PATCH 0/5] replace build code for unit test... David Marchand
- Re: [RFC PATCH 0/5] replace build code for unit ... Patrick Robb
- Re: [RFC PATCH 0/5] replace build code for u... Bruce Richardson
- Re: [RFC PATCH 0/5] replace build code f... Patrick Robb
- [PATCH v2 0/8] expand list of optional libraries Bruce Richardson
- [PATCH v2 1/8] app/test: add new macros for vari... Bruce Richardson
- [PATCH v2 2/8] app/test: tag tests with the test... Bruce Richardson
- [PATCH v2 3/8] app/test: make telemetry data tes... Bruce Richardson
- [PATCH v2 4/8] app/test: build using per-file de... Bruce Richardson
- [PATCH v2 5/8] app/test: define unit tests suite... Bruce Richardson
- [PATCH v2 6/8] examples/l3fwd: make eventdev an ... Bruce Richardson
- [PATCH v2 7/8] build: make most device classes o... Bruce Richardson