Describe the bug
It seems as if the teardown function is not run for the warmup of the benchmarks? I can see an output directory is created before running the benchmarks and not deleted. The output directories created during the benchmarks are correctly deleted with the teardown function.
To Reproduce
In an environment with asv run asv run -q. Once the benchmarks are done, check ~/.brainglobe/workflows/cellfinder. There shouldn't be any output directories in there (with name in the format cellfinder_output_yyyymmdd_hhmmss) after running the benchmarks, but there seems to be one whose timestamp indicates it was created before the benchmarks are run.
Expected behaviour
A clear and concise description of what you expected to happen.
Log file
Please attach the log file if relevant (e.g. output/cellfinder_2019-12-17_13-29-46.log)
Screenshots
If applicable, add screenshots to help explain your problem.
Computer used (please complete the following information):
OS: [e.g. Linux, Windows, macOS] For macOS, please specify if you have an Intel or M1 CPU (M1 is likely if your mac is new).
Version [e.g. 18.04]
Hardware specs [e.g. 128 GB RAM, Xeon 4114 CPU].
Additional context
Add any other context about the problem here.
Describe the bug It seems as if the teardown function is not run for the warmup of the benchmarks? I can see an output directory is created before running the benchmarks and not deleted. The output directories created during the benchmarks are correctly deleted with the teardown function.
To Reproduce In an environment with
asvrunasv run -q. Once the benchmarks are done, check~/.brainglobe/workflows/cellfinder. There shouldn't be any output directories in there (with name in the formatcellfinder_output_yyyymmdd_hhmmss) after running the benchmarks, but there seems to be one whose timestamp indicates it was created before the benchmarks are run.Expected behaviour A clear and concise description of what you expected to happen.
Log file Please attach the log file if relevant (e.g.
output/cellfinder_2019-12-17_13-29-46.log)Screenshots If applicable, add screenshots to help explain your problem.
Computer used (please complete the following information):
Additional context Add any other context about the problem here.