Skip to content

CI: derive the workspace path instead of hardcoding the repo name - #38

Merged
jdatcmd merged 1 commit into
masterfrom
ci-workspace-path
Aug 26, 2026
Merged

CI: derive the workspace path instead of hardcoding the repo name#38
jdatcmd merged 1 commit into
masterfrom
ci-workspace-path

Conversation

@jdatcmd

@jdatcmd jdatcmd commented Aug 26, 2026

Copy link
Copy Markdown
Collaborator

The break

Every CI job on the current master fails before running a test:

chmod: cannot access '/home/runner/work/PL-php': No such file or directory
##[error]Process completed with exit code 1.

The "Run the regression tests" and ASAN steps make the workspace traversable for the postgres user by chmod'ing each ancestor directory, and named the middle one literally as /home/runner/work/PL-php. Renaming the repository to plPHP moved the checkout to /home/runner/work/plPHP/plPHP, so that path no longer exists. The step runs under bash -e, so the failed chmod takes the whole job down: all 11 matrix jobs plus ASAN.

The fix

Use $(dirname "$GITHUB_WORKSPACE"), which resolves to the same directory whatever the repository is called. No other behavior changes, and this is the only place the old name was hardcoded outside documentation.

This blocks every open PR, so it wants to land first.

🤖 Generated with Claude Code

The regression-test steps make the workspace traversable for the
postgres user by chmod'ing each ancestor directory, and named the middle
one literally: /home/runner/work/PL-php.  Renaming the repository to
plPHP moved the checkout to /home/runner/work/plPHP/plPHP, so that chmod
now fails with "cannot access", and since the step runs under "bash -e"
every matrix job and the ASAN job fail before a single test runs.

Use $(dirname "$GITHUB_WORKSPACE") instead, which is the same directory
whatever the repository is called.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@jdatcmd
jdatcmd merged commit 7e12d45 into master Aug 26, 2026
12 checks passed
@jdatcmd
jdatcmd deleted the ci-workspace-path branch August 26, 2026 17:11
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.

2 participants