# Could we prevent the pv., pvcs. and pvcrs. test from running simultaneously

**URL:** https://discourse.paraview.org/t/could-we-prevent-the-pv-pvcs-and-pvcrs-test-from-running-simultaneously/1151
**Category:** Development
**Created:** [January 18, 2019, 6:00pm UTC](https://discourse.paraview.org/t/could-we-prevent-the-pv-pvcs-and-pvcrs-test-from-running-simultaneously/1151 "2019-01-18T18:00:27Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![Andy\_Bauer](https://discourse.paraview.org/user_avatar/discourse.paraview.org/andy_bauer/32/5442_2.png) [@Andy\_Bauer](https://discourse.paraview.org/u/Andy_Bauer)
#### Post date: [January 18, 2019, 6:00pm UTC](https://discourse.paraview.org/t/could-we-prevent-the-pv-pvcs-and-pvcrs-test-from-running-simultaneously/1151/1 "2019-01-18T18:00:27Z")

</div>

Could we automatically prevent the pv._, pvcs._ and pvcrs.\* tests from running simultaneously? For example, the **SaveTSV** test is currently forced to run in serial because it writes out a .tsv file and then reads it back in. If the pv., pvcs. and/or pvcrs versions are running simultaneously it is likely to corrupt the .tsv file for one of the tests and cause a failure but I think it’s a bit overkill to mark the test to be run in serial since every other test will not affect this test. There’s also the SaveTXT and SaveCSV test which should also be similarly marked but are not and probably others as well. If we did it automatically for these tests it would probably reduce false test failures due to test collisions like this while probably also decreasing the time for running all of the tests in parallel.

Thanks,  
Andy

---

<div class="post-metadata">

### Author: ![ben.boeckel](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/b/ea5d25/32.png) [@ben.boeckel](https://discourse.paraview.org/u/ben.boeckel)
#### Post date: [January 22, 2019, 5:38pm UTC](https://discourse.paraview.org/t/could-we-prevent-the-pv-pvcs-and-pvcrs-test-from-running-simultaneously/1151/2 "2019-01-22T17:38:33Z")

</div>

It’s possible to set the `RESOURCE_LOCK` property on the tests that reuse the same paths. The ParaView testing macros don’t provide helpers for this, but nothing is wrong with calling `set_tests_properties` after creating the tests.

---

<div class="post-metadata">

### Author: ![Andy\_Bauer](https://discourse.paraview.org/user_avatar/discourse.paraview.org/andy_bauer/32/5442_2.png) [@Andy\_Bauer](https://discourse.paraview.org/u/Andy_Bauer)
#### Post date: [January 22, 2019, 7:30pm UTC](https://discourse.paraview.org/t/could-we-prevent-the-pv-pvcs-and-pvcrs-test-from-running-simultaneously/1151/3 "2019-01-22T19:30:24Z")

</div>

Ok – have an [MR](https://gitlab.kitware.com/paraview/paraview/merge_requests/2973) for it which is now merged into master.