From a516b9d66fd073aff1a9352aecca1c345fbef9ff Mon Sep 17 00:00:00 2001
From: Morris Jette <jette@schedmd.com>
Date: Tue, 6 Dec 2016 10:43:59 -0700
Subject: [PATCH] Describe a configuration that could cause test to fail
There were already several configurations that could cause this test
to fail. I just added another.
---
testsuite/expect/test1.84 | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/testsuite/expect/test1.84 b/testsuite/expect/test1.84
index e0faddc3470..1a3bca0c35a 100755
--- a/testsuite/expect/test1.84
+++ b/testsuite/expect/test1.84
@@ -189,7 +189,7 @@ if {$cpu_cnt != $task_cnt} {
if {$cpu_cnt != $task_cnt} {
send_user "FAILURE: Should have run $cpu_cnt tasks (one per core) "
send_user "instead of $task_cnt tasks\n"
- send_user "NOTE: This could be due to memory limit per allocated CPU, MaxCPUsPerNode, or OverSubscribe=FORCE\n\n"
+ send_user "NOTE: This could be due to memory limit per allocated CPU, MaxCPUsPerNode, CR_ONE_TASK_PER_CORE, or OverSubscribe=FORCE\n\n"
set exit_code 1
}
if {$cpu_cnt < 2} {
--
GitLab