setup-env.sh only works properly if run from the repo root
@ilumsden is already working on this.
Since Jun 4, 2025.
- Dominant language
- Python
- Stars
- 78
- Forks
- 52
- Avg merge
- 4d 19m
- Merged PRs (30d)
- 10
Description
**Describe the bug**
When you source `setup-env.sh` from any directory except the root of your benchpark clone, `PATH` is not updated correctly. For example, when a user named `jovyan` sources the script from their home directory, the script adds `/home/jovyan/bin` to `PATH` (instead of `/home/jovyan/benchpark/bin`), resulting in:
```
bash: benchpark: command not found
```
**To Reproduce**
Steps to reproduce the behavior:
1. Run `source ${BENCHPARK_ROOT_DIR}/setup-env.sh` from any directory except `${BENCHPARK_ROOT_DIR}`
2. Run any benchpark command
**Expected behavior**
Sourcing `setup-env.sh` properly sets `PATH` regardless of what directory you are in.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.