Open
Description
Describe the bug
The wrapper script for Runner.Listener
does not propagate the exit code when invoked, and always exists 0.
This makes it impossible for any systemd unit error handling to correctly handle the runner exit status.
Submitted a fix here, #2719 but it has not had any attention in over three weeks.
To Reproduce
Steps to reproduce the behavior:
- Force the runner listener process to exit non-zero (I did this via an invalid registration)
- Allow any retries to exhaust.
- Check the exit code of the process, note that it is 0.
Expected behavior
The error code is propagated to the caller.
Runner Version and Platform
Version of your runner?
v2.308.0
OS of the machine running the runner? OSX/Windows/Linux/...
Linux
What's not working?
N/A
Job Log Output
N/A
Runner and Worker's Diagnostic Logs
N/A
Activity