Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Output folder created before running benchmarks #98

Open
sfmig opened this issue Apr 25, 2024 · 0 comments
Open

[BUG] Output folder created before running benchmarks #98

sfmig opened this issue Apr 25, 2024 · 0 comments
Assignees
Labels
bug Something isn't working

Comments

@sfmig
Copy link
Contributor

sfmig commented Apr 25, 2024

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.

@sfmig sfmig added the bug Something isn't working label Apr 25, 2024
@sfmig sfmig self-assigned this Apr 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant