On Fri, Nov 19, 2021 at 5:54 PM Dumitrescu, Cristian <cristian.dumitre...@intel.com> wrote: > On a different point, we should probably tweak our autotests to differentiate > between logical failures and those failures related to resources not being > available, and flag the test result accordingly in the report. For example, > if memory allocation fails, the test should be flagged as "Not enough > resources" instead of simply "Failed". In the first case, the next step > should be fixing the test setup, while in the second case the next step > should be fixing the code. What do people think on this?
In such case, the test must return TEST_SKIPPED. I did a pass for cores count / specific hw requirements, some time ago. See https://git.dpdk.org/dpdk/commit/?id=e0f4a0ed4237 -- David Marchand
