tests: configure 32 mb physmem 27/24127/2
authorDave Barach <dave@barachs.net>
Wed, 25 Dec 2019 14:24:58 +0000 (09:24 -0500)
committerAndrew Yourtchenko <ayourtch@gmail.com>
Thu, 2 Jan 2020 16:29:19 +0000 (16:29 +0000)
Absolutely nothing good happens when we force the kernel to briefly
map and then unmap 16gb as vpp starts. Effect exacerbated when
TEST_JOBS = 20...40, and so forth.

Type: test

Signed-off-by: Dave Barach <dave@barachs.net>
Change-Id: Id8e3ce1763cad3a0891d5d6c8d2c1e3e610682d7

test/framework.py
test/test_vlib.py

index 7d1955f..e08c9a1 100644 (file)
@@ -381,6 +381,7 @@ class VppTestCase(unittest.TestCase):
                            "prefix", cls.shm_prefix, "}", "cpu", "{",
                            "main-core", str(cpu_core_number),
                            cls.worker_config, "}",
+                           "physmem", "{", "max-size", "32m", "}",
                            "statseg", "{", "socket-name", cls.stats_sock, "}",
                            "socksvr", "{", "socket-name", cls.api_sock, "}",
                            "plugins",
index 33dc602..82cf6ab 100644 (file)
@@ -24,8 +24,7 @@ class TestVlib(VppTestCase):
     def tearDown(self):
         super(TestVlib, self).tearDown()
 
-    # @unittest.skipUnless(running_extended_tests, "part of extended tests")
-
+    @unittest.skipUnless(running_extended_tests, "part of extended tests")
     def test_vlib_main_unittest(self):
         """ Vlib main.c Code Coverage Test """