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

pip3 installed software is not available in PATH in macos-12 #6496

Closed
2 of 11 tasks
general-kroll-4-life opened this issue Oct 31, 2022 · 7 comments
Closed
2 of 11 tasks
Assignees
Labels
bug report investigate Collect additional information, like space on disk, other tool incompatibilities etc. OS: macOS

Comments

@general-kroll-4-life
Copy link

Description

I am using pip3 to install robot framework and other python packages. In the macos-11 image, they are all available to subsequent steps. In the macos-12 image I encountered, at least robot framework was not available.

Platforms affected

  • Azure DevOps
  • GitHub Actions - Standard Runners
  • GitHub Actions - Larger Runners

Runner images affected

  • Ubuntu 18.04
  • Ubuntu 20.04
  • Ubuntu 22.04
  • macOS 10.15
  • macOS 11
  • macOS 12
  • Windows Server 2019
  • Windows Server 2022

Image version and build link

Current runner version: '2.298.2'
...
Image: macos-12
Version: 20221027.1

The below link is a private build to jog my memory, please see screen grabs also:

https://github.com/stackql/stackql-devel/actions/runs/3365385197/jobs/5580799140

Screen Shot 2022-11-01 at 10 44 45 am

Screen Shot 2022-11-01 at 10 47 26 am

Is it regression?

No

Expected behavior

Packages installed with pip3 (eg robot framework) should be available to subsequent steps, as per macos-11.

Actual behavior

Getting a robot: command not found error.

Repro steps

Using the runner cited:

  1. pip3 install robotframework
  2. in a subsequent step robot --version
@igorboskovic3
Copy link
Contributor

Hi @general-kroll-4-life, we will take a look.

@igorboskovic3 igorboskovic3 added OS: macOS investigate Collect additional information, like space on disk, other tool incompatibilities etc. and removed needs triage labels Nov 1, 2022
@al-cheb
Copy link
Contributor

al-cheb commented Nov 1, 2022

Hey @general-kroll-4-life.

We have migrated python installation to use macOS universal package. Our recommendation is to use setup-python task or python3 -m syntax:

setup-python:

      - uses: actions/setup-python@v4
        with:
          python-version: '3.11' 
      - run: |
          pip3 install robotframework
      - run: |
          robot --version || true
      - run: |
          python3 -m robot --version || true

image

https://robotframework.org/robotframework/latest/RobotFrameworkUserGuide.html#installing-python-on-macos
http://robotframework.org/robotframework/latest/RobotFrameworkUserGuide.html#return-codes

251 Help or version information printed.

python3 -m syntax:

      - run: |
          pip3 install robotframework
      - run: |
          python3 -m robot --version || true

image

rhysd added a commit to rhysd/actionlint that referenced this issue Nov 1, 2022
@general-kroll-4-life
Copy link
Author

Hey @general-kroll-4-life.

We have migrated python installation to use macOS universal package. Our recommendation is to use setup-python task or python3 -m syntax:

setup-python:

      - uses: actions/setup-python@v4
        with:
          python-version: '3.11' 
      - run: |
          pip3 install robotframework
      - run: |
          robot --version || true
      - run: |
          python3 -m robot --version || true

image

https://robotframework.org/robotframework/latest/RobotFrameworkUserGuide.html#installing-python-on-macos http://robotframework.org/robotframework/latest/RobotFrameworkUserGuide.html#return-codes

251 Help or version information printed.
python3 -m syntax:

      - run: |
          pip3 install robotframework
      - run: |
          python3 -m robot --version || true

image

Cheers all

@al-cheb
Copy link
Contributor

al-cheb commented Nov 2, 2022

Close as by design.

@al-cheb al-cheb closed this as completed Nov 2, 2022
@general-kroll-4-life
Copy link
Author

@al-cheb this same thing is now happening in a macos-11 runnner; is this intentional?

@al-cheb
Copy link
Contributor

al-cheb commented Nov 3, 2022

@al-cheb this same thing is now happening in a macos-11 runnner; is this intentional?

Yep, we use the same universal package.

kleisauke added a commit to kleisauke/libvips-packaging that referenced this issue Nov 3, 2022
Since GitHub actions migrated the Python installation to a universal
package, which no longer adds the pip3 site-packages to the PATH, see:
actions/runner-images#6496
lovell pushed a commit to lovell/sharp-libvips that referenced this issue Nov 3, 2022
Since GitHub actions migrated the Python installation to a universal
package, which no longer adds the pip3 site-packages to the PATH, see:
actions/runner-images#6496
@kleisauke
Copy link

Is this a duplicate of issue #6507, which was fixed with commit f6632ff (but not deployed at the time of writing)? If so, the workaround in comment #6507 (comment) or waiting until the new macOS images are deployed would also fix this. 😅

chris-durand added a commit to salkinium/modm that referenced this issue Jan 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug report investigate Collect additional information, like space on disk, other tool incompatibilities etc. OS: macOS
Projects
None yet
Development

No branches or pull requests

4 participants