Steps to replicate the issue (include links if applicable):
- run git checkout main on jobs-framework-api repo.
- run git pull origin main to ensure the repo is up to date.
- now try submitting a job for example toolforge-jobs --debug run anotherjob --command ./sleep40.sh --image tf-python39 (should already have the jobs-framework-cli already installed.
After submitting the job, running toolforge-jobs show anotherjob shows that the job failed with exist status 127. job logs are also not created.
What should have happened instead?:
the job should succeed and logs should be created.
Software version (skip for WMF-hosted wikis like Wikipedia):
Other information (browser name/version, screenshots, etc.):
Investigating this a bit seems to point to the bug being introduced by this patch https://gerrit.wikimedia.org/r/c/cloud/toolforge/jobs-framework-api/+/783439. Another person can confirm this claim.