Skip these futures when CHPL_COMM != none

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 ---- Signed-off-by: Lydia Duncan <[email protected]>
chapel-lang · Jul 7, 2024 · 78afe28 · 78afe28
1 parent 47be0e3
commit 78afe28
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