[GH-ISSUE #368] Error better when failing. #260

New issue

Closed

opened 2026-03-01 21:41:52 +03:00 by kerem · 1 comment

kerem commented

2026-03-01 21:41:52 +03:00

Owner

Originally created by @ChrisScottThomas on GitHub (Sep 16, 2020).
Original GitHub issue: https://github.com/nektos/act/issues/368

I had is issue in a workflow where job2 required job1 to succeed, and I had misspelled jib1.

When Act ran I got back:

act -n
  shell: /bin/bash -e {0}
time="2020-09-16T14:46:06Z" level=fatal msg="Unable to build dependency graph!"
##[error]Process completed with exit code 1.

Which is not helpful. Ideally this should run and actually highlight the error. At least highlight the file and line where it found the problem.
When I fixed the spelling mistake, it ran perfectly.

I should say I am running Act as a GitHub Action Workflow, in order to validate other workflows, as there is nothing out there that does this. Act failing at a mistake that would otherwise fail down the line, is good. Just not helpful in debugging. I also ran this locally, getting the same issue.

Originally created by @ChrisScottThomas on GitHub (Sep 16, 2020). Original GitHub issue: https://github.com/nektos/act/issues/368 I had is issue in a workflow where `job2` required `job1` to succeed, and I had misspelled `jib1`. When Act ran I got back: ``` act -n shell: /bin/bash -e {0} time="2020-09-16T14:46:06Z" level=fatal msg="Unable to build dependency graph!" ##[error]Process completed with exit code 1. ``` Which is not helpful. Ideally this should run and actually highlight the error. At least highlight the file and line where it found the problem. When I fixed the spelling mistake, it ran perfectly. I should say I am running Act as a GitHub Action Workflow, in order to validate other workflows, as there is nothing out there that does this. Act failing at a mistake that would otherwise fail down the line, is good. Just not helpful in debugging. I also ran this locally, getting the same issue.

kerem

2026-03-01 21:41:52 +03:00

closed this issue
added the
stale
label

kerem commented

2026-03-01 21:41:53 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Nov 16, 2020):

Issue is stale and will be closed in 7 days unless there is new activity

@github-actions[bot] commented on GitHub (Nov 16, 2020): Issue is stale and will be closed in 7 days unless there is new activity

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/act#260

No description provided.

Rows
Columns