mirror of
https://github.com/nektos/act.git
synced 2026-04-26 01:15:51 +03:00
[GH-ISSUE #1885] failed to identify reference (tag/branch) for the checked-out revision #912
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#912
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 @andre15silva on GitHub (Jun 26, 2023).
Original GitHub issue: https://github.com/nektos/act/issues/1885
Bug report info
Command used with act
Describe issue
Sometines (not always), when running
actin parallel there occur failures in checking out either the repository or some actions (e.g,setup-java,setup-python).We have tried and this also occurs in older version (
0.2.44,0.2.45), with and without the cache server feature (and using the workaround suggested in https://github.com/nektos/act/issues/1825#issuecomment-1606063316)Link to GitHub repository
https://github.com/Nfsaavedra/crawlergpt-test-repo
Workflow content
Relevant log output
Additional information
No response
@andre15silva commented on GitHub (Jun 26, 2023):
I have tried with setting a random artifact server path with a random port (
0) for each execution, but still face the same issue sometimes:@ChristopherHX commented on GitHub (Jun 26, 2023):
Yes, act's git actions download cache isn't process / thread safe. I confirm this defect.
If an action has no update available this problem doesn't appear after one job has cached the action.
Wait who returns this error?
This is a warning. The function logging this message can not return any error.
"Relevant log output", I have a different opinion about how relevant the missing part of your log is. It misses why "Error: Job 'test' failed" has been returned, might has not been logged.
Or is the bug report because of a warning?
@andre15silva commented on GitHub (Jun 29, 2023):
Hi @ChristopherHX ,
Thanks a lot! Indeed, this was the problem. We didn't realize that the option
--cache-server-pathwould not set a different cache directory (as one can do by settingXDG_CACHE_HOMEor using the new option introduced in https://github.com/nektos/act/pull/1863).Now that we have a different action cache directory for each worker it runs without any issue :))
Regarding the other errors, we noticed that we also had a bug in our code that could end up with two distinct
actruns on the same repository/working directory (but on different commits). This was likely the cause of the checkout errors/warnings at the repository level. Now that we have fixed it we don't observe them anymore.