-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Getting "Caching for 'false' is not supported" error when using 3rd party action #2243
Comments
Same issue here [Build Stacer Application/Build App] 💬 ::debug::Found tool in cache Python 3.11.9 x64
| Successfully set up CPython (3.11.9)
[Build Stacer Application/Build App] ❓ ::endgroup::
[Build Stacer Application/Build App] ❗ ::error::Caching for 'false' is not supported
[Build Stacer Application/Build App] ❌ Failure - Main Setup Python
[Build Stacer Application/Build App] ⚙ ::set-env:: pythonLocation=/opt/hostedtoolcache/Python/3.11.9/x64
[Build Stacer Application/Build App] ⚙ ::set-env:: PKG_CONFIG_PATH=/opt/hostedtoolcache/Python/3.11.9/x64/lib/pkgconfig
[Build Stacer Application/Build App] ⚙ ::set-env:: Python_ROOT_DIR=/opt/hostedtoolcache/Python/3.11.9/x64
[Build Stacer Application/Build App] ⚙ ::set-env:: Python2_ROOT_DIR=/opt/hostedtoolcache/Python/3.11.9/x64
[Build Stacer Application/Build App] ⚙ ::set-env:: Python3_ROOT_DIR=/opt/hostedtoolcache/Python/3.11.9/x64
[Build Stacer Application/Build App] ⚙ ::set-env:: LD_LIBRARY_PATH=/opt/hostedtoolcache/Python/3.11.9/x64/lib
[Build Stacer Application/Build App] ⚙ ::set-output:: python-version=3.11.9
[Build Stacer Application/Build App] ⚙ ::set-output:: python-path=/opt/hostedtoolcache/Python/3.11.9/x64/bin/python
[Build Stacer Application/Build App] ⚙ ::add-path:: /opt/hostedtoolcache/Python/3.11.9/x64
[Build Stacer Application/Build App] ⚙ ::add-path:: /opt/hostedtoolcache/Python/3.11.9/x64/bin
[Build Stacer Application/Build App] exitcode '1': failure
[Build Stacer Application/Build App] ❌ Failure - Main Install Qt
[Build Stacer Application/Build App] ⚙ ::set-env:: pythonLocation=/opt/hostedtoolcache/Python/3.11.9/x64
[Build Stacer Application/Build App] ⚙ ::set-env:: PKG_CONFIG_PATH=/opt/hostedtoolcache/Python/3.11.9/x64/lib/pkgconfig
[Build Stacer Application/Build App] ⚙ ::set-env:: Python_ROOT_DIR=/opt/hostedtoolcache/Python/3.11.9/x64
[Build Stacer Application/Build App] ⚙ ::set-env:: Python2_ROOT_DIR=/opt/hostedtoolcache/Python/3.11.9/x64
[Build Stacer Application/Build App] ⚙ ::set-env:: Python3_ROOT_DIR=/opt/hostedtoolcache/Python/3.11.9/x64
[Build Stacer Application/Build App] ⚙ ::set-env:: LD_LIBRARY_PATH=/opt/hostedtoolcache/Python/3.11.9/x64/lib
[Build Stacer Application/Build App] ⚙ ::set-output:: python-version=3.11.9
[Build Stacer Application/Build App] ⚙ ::set-output:: python-path=/opt/hostedtoolcache/Python/3.11.9/x64/bin/python
[Build Stacer Application/Build App] ⚙ ::add-path:: /opt/hostedtoolcache/Python/3.11.9/x64
[Build Stacer Application/Build App] ⚙ ::add-path:: /opt/hostedtoolcache/Python/3.11.9/x64/bin
[Build Stacer Application/Build App] exitcode '1': failure``` |
It is failing, whatever value you set for 'cache' when using jurplel/install-qt-action@v3 So, I do not see the way to use this action with act This is the interesting code:
Uncomment last two lines to test with 'true' |
My veto against not deriving the inputs context from env variables shaped like We have an ugly action input pollution, in this example is the default value has not been taken out of action.yml due to beeing shadowed by an composite action. If you have time and push this problem forward to a solution, we need your time to test this change carefully: #2348 You can always download act as an artifacts from the test Github Actions Workflow triggered by the PR or build locally. I for my part need to create testdata to cover the odd bits of the code in act, better coverage can prevent bad design decisions to be merged due to broken tests. |
Bug report info
Command used with act
Describe issue
I have a workflow which uses the install-qt-action action which I'd like to run locally. Sadly this GitHub action seems to setup some Python stuff which act complains about.
Link to GitHub repository
No response
Workflow content
Relevant log output
Additional information
I don't have a lot of experience with GitHub actions yet, please forgive me if this isn't a really a bug. Might it be due to act not supporting caching?
The text was updated successfully, but these errors were encountered: