-
-
Notifications
You must be signed in to change notification settings - Fork 172
Closed
Description
I was pinged in Slack by @Qard about the lint job failing repeatedly. I took it to #nodejs-build and you can see the conversation at https://openjs-foundation.slack.com/archives/C03BJP63CH0/p1680236357000469.
test-ibm-ubuntu-1804-x64-1 was getting a lot of this:
python3 -m pip install --no-user --upgrade -t tools/pip/site-packages flake8 || \
21:24:11 python3 -m pip install --no-user --upgrade --system -t tools/pip/site-packages flake8
21:24:12
21:24:12 Usage:
21:24:12 /usr/bin/python3 -m pip install [options] <requirement specifier> [package-index-options] ...
21:24:12 /usr/bin/python3 -m pip install [options] -r <requirements file> [package-index-options] ...
21:24:12 /usr/bin/python3 -m pip install [options] [-e] <vcs project url> ...
21:24:12 /usr/bin/python3 -m pip install [options] [-e] <local project path> ...
21:24:12 /usr/bin/python3 -m pip install [options] <archive url/path> ...
21:24:12
21:24:12 no such option: --no-user
When I took it offline and the job ended up running on test-equinix-ubuntu2204-x64-1, it passed.
@nodejs/python (I'm guessing/hoping @cclauss will have an immediate recommended/preferred solution. I'm not sure if pip doesn't support no-user anymore or if the version of pip we're running on that machine must be an old one or something else.)
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels