On 18/02/26 10:09 pm, AnishMulay wrote: > Currently, the migration test asserts that numa_available() returns 0. > On systems where NUMA is not available (returning -1), such as certain > ARM64 configurations or single-node systems, this assertion fails and > crashes the test. > > Update the test to check the return value of numa_available(). If it > is less than 0, skip the test gracefully instead of failing. > > This aligns the behavior with other MM selftests (like rmap) that > skip when NUMA support is missing. > > Signed-off-by: AnishMulay <[email protected]> > ---
Reviewed-by: Dev Jain <[email protected]> > tools/testing/selftests/mm/migration.c | 3 ++- > 1 file changed, 2 insertions(+), 1 deletion(-) > > diff --git a/tools/testing/selftests/mm/migration.c > b/tools/testing/selftests/mm/migration.c > index ee24b88c2b248..60e78bbfc0e3e 100644 > --- a/tools/testing/selftests/mm/migration.c > +++ b/tools/testing/selftests/mm/migration.c > @@ -36,7 +36,8 @@ FIXTURE_SETUP(migration) > { > int n; > > - ASSERT_EQ(numa_available(), 0); > + if (numa_available() < 0) > + SKIP(return, "NUMA not available"); > self->nthreads = numa_num_task_cpus() - 1; > self->n1 = -1; > self->n2 = -1;
