mirror of
https://github.com/nektos/act.git
synced 2026-04-26 09:25:54 +03:00
[GH-ISSUE #1993] Unexpected failure due to warning "Could not find any stages to run" #957
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#957
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 @ericcornelissen on GitHub (Sep 5, 2023).
Original GitHub issue: https://github.com/nektos/act/issues/1993
Bug report info
Command used with act
Command:
Additional configuration (
.actrc):Describe issue
I'm expected no error because:
needs:) just fine.act --list, see:I also wasn't able to figure out if I was doing something wrong from the
--helpmessage.Link to GitHub repository
https://github.com/ericcornelissen/git-tag-annotation-action
Workflow content
Relevant log output
Additional information
act, in addition to the repo above:@dannystaple commented on GitHub (Sep 6, 2023):
I can 100% reproduce this in v0.2.50, but not in v0.2.49.
In v0.2.50 I see the warnings and errors:
In v.0.2.49:
@damarvin commented on GitHub (Sep 16, 2023):
Same here: 0.2.50 gives
Error: Could not find any stages to run., 0.2.49 does not.@fharper commented on GitHub (Sep 19, 2023):
I have the same error, but my workflows are running correctly anyway.
@provEdgardoGutierrez commented on GitHub (Sep 20, 2023):
I was able to resolve these warnings/errors by specifying the exact path to the job I was trying to run with the
-Wflag.Command that produced errors ❌
Output
Command that resolved errors ✅
Output
I didn't dive in too much further since this resolved my specific issues case, but I wonder if it has something to do with a mismatch local resources vs all jobs OR perhaps the warning about:
(This warning popped up for me when I ran
act --list)@fharper commented on GitHub (Sep 20, 2023):
Not for me, just when I run the job.
Also working for me, not sure why as it was never required before, and as I mention previously, the job is running for me even with the warnings.
@provEdgardoGutierrez commented on GitHub (Sep 20, 2023):
Yeah mine worked with the warnings too, but it annoyed me 😆
@tigitlabs commented on GitHub (Sep 25, 2023):
Same here, for now I fixed my CI by pinning the version:
gh extension install https://github.com/nektos/gh-act --pin v0.2.49@andrewvaughan commented on GitHub (Oct 3, 2023):
I wanted to add that I'm also running into this issue on
v0.2.51- I don't know if I have much else to add. It's very frustrating.Edit: I've also confirmed that I do not have this issue if I revert to
v0.2.49For anyone coming here using Homebrew, it's a PITA to now install specific versions of packages, for whatever reason. This is how I did it:
@SlimDeluxe commented on GitHub (Nov 29, 2023):
Still getting this on 0.2.54, solved by specifying the workflow file as suggested by @provEdgardoGutierrez.
Gives warnings:
Works normally:
@zero1zero commented on GitHub (Oct 6, 2024):
Just for help for anyone coming here from google. I saw this specific error when my workflow didnt have an
onproperty.@gerry-kavanagh-hpe commented on GitHub (Oct 23, 2024):
FYI, act version 0.2.68 still fails with
on: workflow_dispatch:Works with file explicitly specified.