Don't run stress tests for lock-async on JVM

Since fixing the ThreadPoolScheduler (commit 8d95402) these tests are dying badly. I'm quite sure, an underlying problem is surfacing now.
rakudo · Mar 7, 2018 · 3259953 · 3259953
1 parent dd2c901
commit 3259953
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/t/spectest.data b/t/spectest.data
@@ -841,8 +841,8 @@ S17-promise/anyof.t
 S17-promise/basic.t
 S17-promise/in.t         # slow
 S17-promise/lock-async.t
-S17-promise/lock-async-stress.t # stress slow
-S17-promise/lock-async-stress2.t # stress slow
+S17-promise/lock-async-stress.t # moar stress slow
+S17-promise/lock-async-stress2.t # moar stress slow
 S17-promise/start.t      # slow
 S17-promise/stress.t     # stress
 S17-promise/then.t