docs: Update GHA workflow timeout to 35 days

content/docs/ref/runner.md

@@ -69,10 +69,10 @@ Any [generic option](/doc/ref) in addition to:
 - **GitHub Actions timeout after a few hours**.
 
   You can request up to
-  [72 hours](https://docs.github.com/en/actions/hosting-your-own-runners/about-self-hosted-runners#usage-limits)
+  [35 days](https://docs.github.com/en/actions/hosting-your-own-runners/about-self-hosted-runners#usage-limits)
   via
-  [`timeout-minutes: 4320`](https://docs.github.com/en/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idtimeout-minutes).
-  CML will helpfully restart GitHub Actions workflows approaching 72 hours
+  [`timeout-minutes: 50400`](https://docs.github.com/en/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idtimeout-minutes).
+  CML will helpfully restart GitHub Actions workflows approaching 35 days
   (you'd need to write your code to save intermediate results to take advantage
   of this).
 

content/docs/self-hosted-runners.md

@@ -35,7 +35,7 @@ environment variables for passing your cloud compute credentials to the
 workflow.
 
 Note that `cml runner` will also automatically restart your jobs (whether from a
-[GitHub Actions 72-hour timeout](https://docs.github.com/en/actions/hosting-your-own-runners/about-self-hosted-runners#usage-limits)
+[GitHub Actions 35 day workflow timeout](https://docs.github.com/en/actions/hosting-your-own-runners/about-self-hosted-runners#usage-limits)
 or a
 [AWS EC2 spot instance interruption](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/spot-interruptions.html)).
 
@@ -67,7 +67,7 @@ jobs:
   train-model:
     needs: deploy-runner
     runs-on: [self-hosted, cml-gpu]
-    timeout-minutes: 4320 # 72h
+    timeout-minutes: 50400 # 35 days
     container:
       image: docker://iterativeai/cml:0-dvc2-base1-gpu
       options: --gpus all