Skip these futures when CHPL_COMM != none (#25432)

[trivial, not reviewed] They appear to not encounter memory issues in those circumstances, so only test them in the scenarios where they fail. Also update the .future files to indicate that the skipifs should be removed when they are resolved Verifying a fresh checkout of the tests behave as expected
chapel-lang · Jul 7, 2024 · 6e69df0 · 6e69df0
2 parents 47be0e3 + 78afe28
commit 6e69df0
Show file tree

Hide file tree

Showing 6 changed files with 9 additions and 0 deletions.
diff --git a/test/types/string/ternaryPlain.future b/test/types/string/ternaryPlain.future
@@ -1,2 +1,4 @@
 bug: strings in ternary expressions will sometimes segfault
 #25032
+
+When this future is resolved, please remove the .skipif file
diff --git a/test/types/string/ternaryPlain.skipif b/test/types/string/ternaryPlain.skipif
@@ -0,0 +1 @@
+CHPL_COMM != none
diff --git a/test/types/string/ternaryPlainRef.future b/test/types/string/ternaryPlainRef.future
@@ -1,2 +1,4 @@
 bug: strings in ternary expressions will sometimes segfault
 #25032
+
+When this future is resolved, please remove the .skipif file
diff --git a/test/types/string/ternaryPlainRef.skipif b/test/types/string/ternaryPlainRef.skipif
@@ -0,0 +1 @@
+CHPL_COMM != none
diff --git a/test/types/string/ternaryReturn.future b/test/types/string/ternaryReturn.future
@@ -1,2 +1,4 @@
 bug: strings in ternary expressions will sometimes segfault
 #25032
+
+When this future is resolved, please remove the .skipif file
diff --git a/test/types/string/ternaryReturn.skipif b/test/types/string/ternaryReturn.skipif
@@ -0,0 +1 @@
+CHPL_COMM != none