mirror of
https://github.com/nektos/act.git
synced 2026-04-26 01:15:51 +03:00
[GH-ISSUE #561] Issue: Error: Could not find a part of the path #379
Labels
No labels
area/action
area/cli
area/docs
area/image
area/runner
area/workflow
backlog
confirmed/not-planned
kind/bug
kind/discussion
kind/external
kind/feature-request
kind/question
meta/duplicate
meta/invalid
meta/need-more-info
meta/resolved
meta/wontfix
meta/workaround
needs-work
pull-request
review/not-planned
size/M
size/XL
size/XXL
stale
stale-exempt
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/act#379
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @sophiederosa on GitHub (Mar 11, 2021).
Original GitHub issue: https://github.com/nektos/act/issues/561
Act version
0.2.20
Expected behaviour
I would expect Act can download this action
Actual behaviour
Unable to process command '[integration-tests/designer/freestyle-elephant/build ] ❓ ##[add-matcher]/actions/actions-setup-python@v2/.github/python.json' successfully.
Error: Could not find a part of the path '/actions/actions-setup-python@v2/.github/python.json'.
Workflow and/or repository
workflow
Steps to reproduce
actoutputLog
@catthehacker commented on GitHub (Mar 11, 2021):
Is that the correct workflow you are using?
This works fine for me
You could also try removing
actcache,rm -rf ~/.cache/act/@sophiederosa commented on GitHub (Mar 11, 2021):
This is the workflow, I just retested it:
Here's a more full output:
It looks like it is fine, but it fails my workflow :( I'll try clearing the cache, but I'm running it on a Github runner during CI so it is re-downloading act before every run, so I wouldn't imagine that would be the issue
@sophiederosa commented on GitHub (Mar 11, 2021):
Let me also try with a different image
@sophiederosa commented on GitHub (Mar 11, 2021):
I tried using this image: catthehacker/ubuntu:act-20.04 and I'm still seeing the error
@catthehacker commented on GitHub (Mar 11, 2021):
Oh ok, that log makes more sense now. I thought that action fails instantly. I think I've seen that issue somewhere already.
@sophiederosa commented on GitHub (Mar 11, 2021):
Oh okay sorry I didn't include those at first! Do you know what the issue is?
@catthehacker commented on GitHub (Mar 11, 2021):
I cannot remember. What else I can recommend is to prune docker volumes.
docker volume pruneto remove unused volumes ordocker system pruneto remove everything what is not used (volumes,containers,images)I'm also trying out to add tests for MacOS so hopefully I can have some basic testing on that OS.
https://github.com/catthehacker/act-fork/runs/2089570985
@sophiederosa commented on GitHub (Mar 11, 2021):
Actually running this on ubuntu if that is helpful info! I'll try the docker prune idea!
@sophiederosa commented on GitHub (Mar 12, 2021):
docker prune wasn't able to help me, so if you remember anything about how to fix this would be really helpful :) thanks!!
@github-actions[bot] commented on GitHub (Apr 12, 2021):
Issue is stale and will be closed in 14 days unless there is new activity
@GabriFedi97 commented on GitHub (Nov 9, 2022):
I'm facing the same issue with the action
actions/setup-go@v3:Has anyone found a workaround to this?
act version: 0.2.33@GabriFedi97 commented on GitHub (Nov 10, 2022):
I finally found the reason and a workaround to the issue. I was running
actinside a GitHub workflow in order to test another workflow, having a step usingactions/setup-go@v3. The action, just like the othersetup-*actions, performs a statement to add a problem matcher in its main.ts. In my case, the execution's output of that line was:##[add-matcher]/run/act/actions/actions-setup-go@v3/matchers.json.That was interpreted by the GitHub runners as a legit add-matcher instruction, so it proceeded trying to add the problem matcher, relying on the file
/run/act/actions/actions-setup-go@v3/matchers.json. However, that file was present only in the container created byactand not on the Host runner, so it ended up throwing the following error:Error: Could not find a part of the path '/run/act/actions/actions-setup-go@v3/matchers.json'.Workaround:
According to the Echoing of Command Input documentation of Github runners, the output keywords that could affect the execution of
act, inside a workflow, are:remove-matcheradd-matcheradd-pathSo filtering away the lines containing those keywords, from the
actoutput, worked for me:act [event name to run] [flags] | grep -v "remove-matcher\|add-matcher\|add-path"