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

Tests leaking parquet files #2847

Closed
2 tasks done
hawkfish opened this issue Dec 29, 2021 · 0 comments · Fixed by #2848
Closed
2 tasks done

Tests leaking parquet files #2847

hawkfish opened this issue Dec 29, 2021 · 0 comments · Fixed by #2848

Comments

@hawkfish
Copy link
Contributor

hawkfish commented Dec 29, 2021

What happens?

If you run the unit or allunit test suites, they leave behind two parquet files: many_ints.parquet and stats.parquet

To Reproduce

$ rm *.parquet
$ make unit; make allunit
$ ls *.parquet

Environment (please complete the following information):

  • OS: [OSX]
  • DuckDB Version: [0.32-dev]
  • DuckDB Client: [zsh]

Before Submitting

  • Have you tried this on the latest master branch?
  • Python: pip install duckdb --upgrade --pre
  • R: install.packages("https://github.com/duckdb/duckdb/releases/download/master-builds/duckdb_r_src.tar.gz", repos = NULL)
  • Other Platforms: You can find binaries here or compile from source.
  • Have you tried the steps to reproduce? Do they include all relevant data and configuration? Does the issue you report still appear there?
Mytherin added a commit to Mytherin/duckdb that referenced this issue Dec 29, 2021
Mytherin added a commit that referenced this issue Dec 30, 2021
Fix #2847: Write parquet files to test dir
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant