{{ message }}
Commit 39cd608
committed
Put back explicit venv activation in Alpine Linux
`busybox sh` does not appear to read commands from a file whose
path is given as the value of `$ENV`, in this situation. I think I
may have misunderstood that; the documentation does not say much
about it and maybe, in Almquist-style shells, it is only read by
interactive shells? I am not sure.
This removes everything about `ENV` and activates the venv in each
step where the venv should be used.
The good news is that the technique did work fully in Cygwin: not
only did `BASH_ENV` work (which was not much in doubt), but using
a virtual environment for all steps that run test code on Cygwin
fixed the problem and allowed all tests to pass. That seems to have
been the reason I didn't reproduce the problem locally: on my local
system I always use a venv in Cygwin since I would otherwise not
have adequate isolation.
Thus, this commit changes only the Alpine workflow and not the
Cygwin workflow.1 parent 4aad37a commit 39cd608
1 file changed
Lines changed: 5 additions & 2 deletions

0 commit comments