Steps to replicate the issue (include links if applicable):
- Create a scheduled job with --timeout set
- Manually run toolforge jobs restart <scheduledjobname>
- The run never times out (the Job does not have the activeDeadlineSeconds set)
This happens for any other non-managed field in the job, as we manually build the job in the code from the cron (https://gitlab.wikimedia.org/repos/cloud/toolforge/jobs-api/-/blob/main/tjf/runtimes/k8s/jobs.py?ref_type=heads#L328).
What happens?:
The job gets created from the scheduled job, but it does not have any timeout set.
What should have happened instead?:
It should create the job with the timeout set properly.
Software version (on Special:Version page; skip for WMF-hosted wikis like Wikipedia):
Other information (browser name/version, screenshots, etc.):