Skip to content

[BUG]: Running tests produces a spurious n directory #1547

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

Open
1 task done
asnare opened this issue May 1, 2025 · 0 comments · May be fixed by #1548
Open
1 task done

[BUG]: Running tests produces a spurious n directory #1547

asnare opened this issue May 1, 2025 · 0 comments · May be fixed by #1548
Assignees
Labels
bug Something isn't working internal technical pr's not end user facing

Comments

@asnare
Copy link
Contributor

asnare commented May 1, 2025

Is there an existing issue for this?

  • I have searched the existing issues

Category of Bug / Issue

Other

Current Behavior

Running the project tests results in a spurious n directory being created in the project root, with a temporary directory structure inside it. (This issue might be limited to macOS.)

Expected Behavior

Running tests shouldn't modify anything within the source project structure; any temporary directories/files should take place within the system-specific temporary directory. (And be cleaned up automatically after tests run.)

Steps To Reproduce

On a mac:

  1. Create a clean development environment:
    HATCH_PYTHON="$(which python3.10)" make clean dev
  2. Verify that there is no n directory.
  3. Run the project tests:
    make test
  4. Observe that an n directory has now been created.

Operating System

macOS

Version

latest via Databricks CLI

@asnare asnare added the bug Something isn't working label May 1, 2025
@asnare asnare self-assigned this May 1, 2025
@asnare asnare linked a pull request May 1, 2025 that will close this issue
@asnare asnare added the internal technical pr's not end user facing label May 1, 2025
@asnare asnare changed the title [BUG]: Running tests produces a spurious 'n' directory [BUG]: Running tests produces a spurious n directory May 1, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working internal technical pr's not end user facing
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant