Right I know - not so good to comment out tests.
BUT they are passing but there is some weirdness
in ssh reconnecting to these nodes that causes CTS false
negatives.
So the nodes are watchdogged (as expected) but when they come
back up cts gets stuck in a loop re-trying to ssh into
them. It odd as a manual ssh works fine.

Basically I think it's more important the we get reliable
testing than have these test in there.

Signed-off-by: Angus Salkeld <[email protected]>
---
 cts/corotests.py |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/cts/corotests.py b/cts/corotests.py
index 514ca3a..60113f5 100644
--- a/cts/corotests.py
+++ b/cts/corotests.py
@@ -1528,9 +1528,9 @@ AllTestClasses.append(SamWdIntegration2)
 AllTestClasses.append(NoWDConfig)
 AllTestClasses.append(WDConfigNoWd)
 AllTestClasses.append(NoWDOnCorosyncStop)
-AllTestClasses.append(WDOnForkBomb)
+#AllTestClasses.append(WDOnForkBomb)
 AllTestClasses.append(WdDeleteResource)
-AllTestClasses.append(RebootOnHighMem)
+#AllTestClasses.append(RebootOnHighMem)
 AllTestClasses.append(ResourcePollAdjust)
 AllTestClasses.append(ServiceLoadTest)
 AllTestClasses.append(MemLeakObject)
-- 
1.7.4

_______________________________________________
Openais mailing list
[email protected]
https://lists.linux-foundation.org/mailman/listinfo/openais

Reply via email to