-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
job matrix, concurrent job execution, job context isolation #1313
Labels
area/runner
Relating to errors in the runner
confirmed/not-planned
Those issues are confirmed, but not planned to be fixed. PR's get reviewed
kind/bug
Something isn't working
stale-exempt
Exempt from stale
Comments
Issue is stale and will be closed in 14 days unless there is new activity |
ChristopherHX
added
area/runner
Relating to errors in the runner
stale-exempt
Exempt from stale
and removed
stale
labels
Sep 23, 2022
Otherwise Lines 133 to 174 in 96ba76b
|
ChristopherHX
added
the
confirmed/not-planned
Those issues are confirmed, but not planned to be fixed. PR's get reviewed
label
Sep 26, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area/runner
Relating to errors in the runner
confirmed/not-planned
Those issues are confirmed, but not planned to be fixed. PR's get reviewed
kind/bug
Something isn't working
stale-exempt
Exempt from stale
Bug report info
Command used with act
Describe issue
From log output, it appears when running there is some issue with correctly assigning and isolating matrix data to the job, this example shows that job 2 is picking up context from job 1:
[Distribute Workflows/act-concurrency-issue-2] 🐳 docker exec cmd=[bash --noprofile --norc -e -o pipefail /var/run/act/workflow/1.sh] user= workdir=./target_repo_1
Job 2, should be assign workdir=./target_repo_2, not 1.
Link to GitHub repository
No response
Workflow content
Relevant log output
Additional information
No response
The text was updated successfully, but these errors were encountered: