We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Found a bug? Maybe our Slack Community can help.
install JQ fails on ARM64 GitHub-hosted runners (linux)
JQ is already available on GitHub runners.
This action can be run with a param to not install if jq is already found, but this action runs it with force
force
A clear and concise description of what you expected to happen.
Steps to reproduce the behavior:
Cannot handle "ARM64" architecture for os "Linux" Error: Process completed with exit code 1.
If applicable, add screenshots or logs to help explain your problem.
Anything that will help us triage the bug will help. Here are some ideas:
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
We've recently bumped dcarbone/install-jq-action to v3 via #73
dcarbone/install-jq-action
v3
Does this still happen on GH-hosted arm64 runners?
arm64
Also,
We (Cloud Posse) use this action on self-hosted runners, where this isn't always the case.
Sorry, something went wrong.
No branches or pull requests
Found a bug? Maybe our Slack Community can help.
Describe the Bug
install JQ fails on ARM64 GitHub-hosted runners (linux)
JQ is already available on GitHub runners.
This action can be run with a param to not install if jq is already found, but this action runs it with
force
Expected Behavior
A clear and concise description of what you expected to happen.
Steps to Reproduce
Steps to reproduce the behavior:
Screenshots
If applicable, add screenshots or logs to help explain your problem.
Environment (please complete the following information):
Anything that will help us triage the bug will help. Here are some ideas:
Additional Context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: