You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
The first job executed on an ephemeral runner always triggers ACTIONS_RUNNER_HOOK_JOB_COMPLETED when this should be reserved for the end of a workflow.
To Reproduce
Steps to reproduce the behavior:
Create an ephemeral runner
have two jobs in a workflow depend on it
First job triggers ACTIONS_RUNNER_HOOK_JOB_COMPLETED, which deletes the runner
Second, or subsequent jobs either wait forever or die part way through as the ephemeral runner is deleted
Expected behavior
ACTIONS_RUNNER_HOOK_JOB_COMPLETED should be only triggered at the end of a designated workflow, not each job.
Runner Version and Platform
Latest, self hosted ephemeral
OS of the machine running the runner? OSX/Windows/Linux/...
Linux, nothing to do with OS
What's not working?
Jobs hang, don't finish, or error out in a workflow in the UI.
Job Log Output
Runner and Worker's Diagnostic Logs
The text was updated successfully, but these errors were encountered:
Describe the bug
The first job executed on an ephemeral runner always triggers ACTIONS_RUNNER_HOOK_JOB_COMPLETED when this should be reserved for the end of a workflow.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
ACTIONS_RUNNER_HOOK_JOB_COMPLETED should be only triggered at the end of a designated workflow, not each job.
Runner Version and Platform
Latest, self hosted ephemeral
OS of the machine running the runner? OSX/Windows/Linux/...
Linux, nothing to do with OS
What's not working?
Jobs hang, don't finish, or error out in a workflow in the UI.
Job Log Output
Runner and Worker's Diagnostic Logs
The text was updated successfully, but these errors were encountered: