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

release-testing #889

Merged
merged 5 commits into from
Oct 4, 2024
Merged

Conversation

Michael-J-Ward
Copy link
Contributor

@Michael-J-Ward Michael-J-Ward commented Oct 1, 2024

Which issue does this PR close?

Closes #804.

Rationale for this change

An error in a prior release wasn't caught because the test instructions

What changes are included in this PR?

  1. The release docs include instructions on testing against test.pypi.org.
  2. The python tests were moved so that they can be run against datafusion installed from pypi.
  3. A clean.sh dev script was added for easily cleaning maturin build artifacts.

Are there any user-facing changes?

No

This change allows us to run the test suite against a release candidate
hosted on test.pypi.org.

```
pip install --extra-index-url https://test.pypi.org/simple/ datafusion==40.0.0

pytest --import-mode=importlib python/tests
```
@Michael-J-Ward Michael-J-Ward changed the title DRAFT: release-testing release-testing Oct 1, 2024
@Michael-J-Ward Michael-J-Ward marked this pull request as ready for review October 3, 2024 14:55
@@ -1,4 +1,4 @@
#!/bin/bash
#!/usr/bin/env bash
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've always seen the former approach of #!/bin/bash. For my own edification, why this change?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

My mental model for env is basically "search $PATH for this executable and use it".

The pattern is more commonly used for things like python, i.e. #!/usr/bin/env python because then the script will automatically use whatever virtual environment you have activated.

It's less commonly used for bash, but I use a pretty niche operating system (NixOS) which doesn't use /bin/bash.

which bash
/nix/store/lmv9b9jbhv68kp5pg467rlgg71lf0zyl-bash-interactive-5.2p26/bin/bashls -l /usr/bin
total 4
lrwxrwxrwx 1 root root 65 Oct  3 06:58 env -> /nix/store/0kg70swgpg45ipcz3pr2siidq9fn6d77-coreutils-9.5/bin/envls -l /bin
total 4
lrwxrwxrwx 1 root root 74 Oct  3 06:58 sh -> /nix/store/qqz0gj9iaidabp7g34r2fb9mds6ahk8i-bash-interactive-5.2p32/bin/sh

@Michael-J-Ward Michael-J-Ward merged commit 5b9e528 into apache:main Oct 4, 2024
23 checks passed
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 this pull request may close these issues.

Docs: Running unit-tests against a release candidate
2 participants