This adds a very strong test, resource-limit-stress, which concurrently spawns and drops 471 communicating processes. It takes ages, so the CI test iterations have been reduced. I've doubled the number of linux CI runners however.
Also add parsing of fabric output to the test harness; this catches a very rare (~1 every 5 cpu hours running the output-data test in a tight loop) hang, see pid 109965 not exiting here:
This adds a very strong test,
resource-limit-stress
, which concurrently spawns and drops 471 communicating processes. It takes ages, so the CI test iterations have been reduced. I've doubled the number of linux CI runners however.Also add parsing of fabric output to the test harness; this catches a very rare (~1 every 5 cpu hours running the
output-data
test in a tight loop) hang, see pid 109965 not exiting here:Also seen with
success
andsuccess-return
.