-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
fix: job's GetMatrixes cannot get the correct matrix #2649
base: master
Are you sure you want to change the base?
Conversation
Thank you for this change, your changed test cache matches my external matrix expansion implementation and my expectations. I approve (not merge) this from my side if / once CI passes |
@silky1313 this pull request has failed checks 🛠 |
seems to fail |
Something is not correct here to my understanding: You seem to break somehow this special case _additionalInclude_0:
strategy:
matrix:
include:
- def: val
runs-on: ubuntu-latest
steps:
- name: Check if the matrix key A exists
run: |
echo $MATRIX
exit ${{matrix.def == 'val' && '0' || '1'}}
env:
MATRIX: ${{toJSON(matrix)}}
- run: |
echo "::set-output name=result::success"
id: result
outputs:
result: ${{ steps.result.outputs.result }} see this yaml file https://github.com/nektos/act/blob/master/pkg/runner/testdata/evalmatrix/push.yml The other infrastructure failure e.g.. exit code 137 can be resolved by me just rerunning the job. confirmed this test has to pass in my point of view running the snapshot shows this bug as well for reference
|
#2648
This Pull requests is mainly to solve this issue