tests: fix bug in sys_vumap test

Ever since a VM allocation strategy change, this test is fully
dysfunctional.  It should be repaired and added to the regular
test set, but that will require some work.

For now, keep it in reasonable shape.

Reported by dcb314.

This closes #153.

Change-Id: Ia57bdfdf6a3fc8d47cae76a0be9881fb4d796f6d

diff --git a/minix/tests/kernel/sys_vumap/vumaptest.c b/minix/tests/kernel/sys_vumap/vumaptest.c
index 0b2627d7a3254940b65d4b4b1f110ccf78cb2c42..0dc00b9391f3e136179af1cdf7de68c9b90cf247 100644 (file)
--- a/minix/tests/kernel/sys_vumap/vumaptest.c
+++ b/minix/tests/kernel/sys_vumap/vumaptest.c
@@ -2,6 +2,7 @@
 #include <minix/drivers.h>
 #include <minix/ds.h>
 #include <sys/mman.h>
+#include <machine/vmparam.h>
 #include <assert.h>
 
 #include "com.h"
@@ -1075,7 +1076,7 @@ static void test_access(void)
 
        expect(r == OK);
        /* Same story but more possibilities. I hope I got this right. */
-       expect(pcount >= 3 || pcount <= 6);
+       expect(pcount >= 3 && pcount <= 6);
        for (i = 0; i < 7; i++)
                expect(is_buf_allocated(&buf[i]));
        expect(pvecp[0].vp_addr = buf[0].phys);