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

Action not working with act #4

Closed
frankplow opened this issue Feb 8, 2023 · 3 comments
Closed

Action not working with act #4

frankplow opened this issue Feb 8, 2023 · 3 comments

Comments

@frankplow
Copy link

When using act, I get the following error:

/entrypoint.sh: line 3: stm32cubeide: command not found
/entrypoint.sh: line 4: headless-build.sh: command not found

The action works fine when run on GitHub, so I think this is due to some idiosyncrasy of act. The reason I am putting this issue here is because act is generally very well supported, including with Docker images. I wonder if there's something this action's Docker image is doing which is throwing it off?

Docker desktop shows two images with IDs 49cf70126577 and 95106a203c9d, both of which seem to have set up fine and installed STM32CubeIDE. Only 49cf70126577 seems to spin up when I run act.

Thanks for this action, it is very useful.

@xanderhendriks
Copy link
Owner

@frankplow I am not a act user myself, but I'm happy to help you fix the problem so it can benefit other people using this action with this tool.
When you mention these 2 ID's are these images created from different versions of the action-build-stm32cubeide? If so, which versions? In that case I can check if there is any obvious difference between the 2.
Alternatively you can create a fork of the repo and modify the entrypoint.sh and add some extra commands that might help identify why it can't find the stm tools.

@frankplow
Copy link
Author

frankplow commented Feb 11, 2023

Looked into this a little more today. STM32CubeIDE is installed, however the ENV PATH layer in the Docker image does not work with act. There is an issue already in the act repo. There is a fix for this in act master but not yet the latest release. There are a number of workarounds but as the fix is imminent, I think the best is for the user to add /opt/st/stm32cubeide_1.10.1/ to the default PATH when instantiating the action:

      - name: Build
        uses: xanderhendriks/[email protected]
        with:
          project-path: '.'
          project-target: '<PROJECT_NAME>'
        env:
          PATH: '/opt/st/stm32cubeide_1.10.1:/opt/hostedtoolcache/node/16.19.0/x64/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/opt/hostedtoolcache/node/16.19.0/x64/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin'

This workaround doesn't require any changes to this action and it sounds like that fix should be in an act release version soon so I think this issue can be closed.

@xanderhendriks
Copy link
Owner

Thanks for looking into this in more detail and posting a work around for as long as it hasn't been fixed in act. Hopefully it will save other people trying to use this action in act some time.

@xanderhendriks xanderhendriks closed this as not planned Won't fix, can't repro, duplicate, stale Aug 21, 2023
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

No branches or pull requests

2 participants