cmake: randomise test runs and clean up the tests directory on successful runs #202
Assignees
Labels
Milestone
Comments
isaac-io
added a commit
that referenced
this issue
Oct 24, 2022
In the case where we create the test path, we should clean up after the run finishes as done in the Makefile, due to garbage that is left behind by tests and accumulates. While at it, randomise test scheduling in order to increase the likelihood of surfacing latent bugs that are hidden by the execution order.
isaac-io
added a commit
that referenced
this issue
Oct 25, 2022
In the case where we create the test path, we should clean up after the run finishes as done in the Makefile, due to garbage that is left behind by tests and accumulates. While at it, randomise test scheduling in order to increase the likelihood of surfacing latent bugs that are hidden by the execution order.
isaac-io
added a commit
that referenced
this issue
Oct 25, 2022
In the case where we create the test path, we should clean up after the run finishes as done in the Makefile, due to garbage that is left behind by tests and accumulates. While at it, randomise test scheduling in order to increase the likelihood of surfacing latent bugs that are hidden by the execution order.
isaac-io
added a commit
that referenced
this issue
Oct 26, 2022
In the case where we create the test path, we should clean up after the run finishes as done in the Makefile, due to garbage that is left behind by tests and accumulates. While at it, randomise test scheduling in order to increase the likelihood of surfacing latent bugs that are hidden by the execution order.
isaac-io
added a commit
that referenced
this issue
Oct 26, 2022
In the case where we create the test path, we should clean up after the run finishes as done in the Makefile, due to garbage that is left behind by tests and accumulates. While at it, randomise test scheduling in order to increase the likelihood of surfacing latent bugs that are hidden by the execution order.
Yuval-Ariel
pushed a commit
that referenced
this issue
Nov 15, 2022
In the case where we create the test path, we should clean up after the run finishes as done in the Makefile, due to garbage that is left behind by tests and accumulates. While at it, randomise test scheduling in order to increase the likelihood of surfacing latent bugs that are hidden by the execution order.
Yuval-Ariel
pushed a commit
that referenced
this issue
Nov 25, 2022
In the case where we create the test path, we should clean up after the run finishes as done in the Makefile, due to garbage that is left behind by tests and accumulates. While at it, randomise test scheduling in order to increase the likelihood of surfacing latent bugs that are hidden by the execution order.
Yuval-Ariel
pushed a commit
that referenced
this issue
Nov 25, 2022
In the case where we create the test path, we should clean up after the run finishes as done in the Makefile, due to garbage that is left behind by tests and accumulates. While at it, randomise test scheduling in order to increase the likelihood of surfacing latent bugs that are hidden by the execution order.
Yuval-Ariel
pushed a commit
that referenced
this issue
Apr 30, 2023
In the case where we create the test path, we should clean up after the run finishes as done in the Makefile, due to garbage that is left behind by tests and accumulates. While at it, randomise test scheduling in order to increase the likelihood of surfacing latent bugs that are hidden by the execution order.
Yuval-Ariel
pushed a commit
that referenced
this issue
May 4, 2023
In the case where we create the test path, we should clean up after the run finishes as done in the Makefile, due to garbage that is left behind by tests and accumulates. While at it, randomise test scheduling in order to increase the likelihood of surfacing latent bugs that are hidden by the execution order.
udi-speedb
pushed a commit
that referenced
this issue
Nov 13, 2023
In the case where we create the test path, we should clean up after the run finishes as done in the Makefile, due to garbage that is left behind by tests and accumulates. While at it, randomise test scheduling in order to increase the likelihood of surfacing latent bugs that are hidden by the execution order.
udi-speedb
pushed a commit
that referenced
this issue
Nov 15, 2023
In the case where we create the test path, we should clean up after the run finishes as done in the Makefile, due to garbage that is left behind by tests and accumulates. While at it, randomise test scheduling in order to increase the likelihood of surfacing latent bugs that are hidden by the execution order.
udi-speedb
pushed a commit
that referenced
this issue
Dec 3, 2023
In the case where we create the test path, we should clean up after the run finishes as done in the Makefile, due to garbage that is left behind by tests and accumulates. While at it, randomise test scheduling in order to increase the likelihood of surfacing latent bugs that are hidden by the execution order.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
After the changes in #103 we are now able to run the tests in parallel and use
/dev/shmautomatically when available. However, tests leave some garbage after them and it accumulates and fills up/dev/shm. Add cleanup code to remove the created directory on successful runs.While at it, ask
ctestto randomise test scheduling in order to increase the likelihood of surfacing bugs.The text was updated successfully, but these errors were encountered: