Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Hook feature - Set up runner step failed when working-directory specified #1808

Closed
retzero opened this issue Apr 5, 2022 · 6 comments · Fixed by #1809
Closed

Hook feature - Set up runner step failed when working-directory specified #1808

retzero opened this issue Apr 5, 2022 · 6 comments · Fixed by #1809
Assignees
Labels
bug Something isn't working

Comments

@retzero
Copy link

retzero commented Apr 5, 2022

Describe the bug
A clear and concise description of what the bug is.

Hello,
I'm trying to use start/complete hook feature. (v 2.289.1)
But it's failing when default working-directory is set in the workflow.
Can you please guide me how to overcome this?

  • My workflow

    defaults:
      run:
        working-directory: 'xyz'
    
    jobs:
      build:
        runs-on: [ "self-hosted" ]
        steps:
          - uses: actions/checkout@v2
  • Error prints

    A job started hook has been configured by the self-hosted runner administrator
    Run '/opt/hook_start.sh'
      shell: /usr/bin/bash -e {0}
    Error: An error occurred trying to start process '/usr/bin/bash' with working directory '/home/github/actions-runner/_work/actions-playground/actions-playground/xyz'. No such file or directory
    

To Reproduce
Steps to reproduce the behavior:

  1. Go to '...'
  2. Run '....'
  3. See error

Expected behavior
A clear and concise description of what you expected to happen.

Runner Version and Platform

Version of your runner?
2.289.1

OS of the machine running the runner? OSX/Windows/Linux/...
Linux (Ubuntu)

What's not working?

Please include error messages and screenshots.

Job Log Output

If applicable, include the relevant part of the job / step log output here. All sensitive information should already be masked out, but please double-check before pasting here.

Runner and Worker's Diagnostic Logs

If applicable, add relevant diagnostic log information. Logs are located in the runner's _diag folder. The runner logs are prefixed with Runner_ and the worker logs are prefixed with Worker_. Each job run correlates to a worker log. All sensitive information should already be masked out, but please double-check before pasting here.

@thboop
Copy link
Collaborator

thboop commented Apr 6, 2022

Thanks for the report @retzero, thats a bug we will get a fix in the next runner version

@retzero
Copy link
Author

retzero commented Apr 6, 2022

@thboop
Thank you for the feedback.
I suggest those steps(Set up runner and Complete runner) not to affect the result of the entire job.

@kkathuri-v
Copy link

kkathuri-v commented Feb 1, 2023

I am using the latest version '2.301.1' for self hosted runner but still facing the same issue. I have also tried specifying the working directory at job level.
@fhammerl - Any ideas?

@nadvolod
Copy link

I'm facing the same issue Error: An error occurred trying to start process '/usr/bin/bash' with working directory '/home/runner/work/java-sdet/java-sdet/java-sdet-bootcamp'. No such file or directory
From https://github.com/ultimate-qa/java-sdet/actions/runs/4218390788/jobs/7322868158

@xposionn
Copy link

facing the same issue

1 similar comment
@bajajdivya
Copy link

facing the same issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants