From 6522da85e46e2783e1d86d7ee5f749943492595d Mon Sep 17 00:00:00 2001 From: Xu Zhao Date: Tue, 20 Feb 2024 11:42:50 -0800 Subject: [PATCH] Further delay the jobs by 1 hour (#2175) Summary: We have found that the K8s cluster will renew all container images at 12PM EST, and at 1PM EST all runners will have the latest container image. It is not clear how to change this behavior. To run the latest container image in our nightly jobs, we have to further delay our nightly job to start at 1PM EST Pull Request resolved: https://github.com/pytorch/benchmark/pull/2175 Reviewed By: aaronenyeshi Differential Revision: D53954402 Pulled By: xuzhao9 fbshipit-source-id: 205668f3f0aa2df75c88e21c9d5a93aab434fd7a --- .github/workflows/userbenchmark-a100.yml | 2 +- .github/workflows/v3-nightly.yml | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/.github/workflows/userbenchmark-a100.yml b/.github/workflows/userbenchmark-a100.yml index 3e9f2f0108..67d4003bdf 100644 --- a/.github/workflows/userbenchmark-a100.yml +++ b/.github/workflows/userbenchmark-a100.yml @@ -1,7 +1,7 @@ name: TorchBench Userbenchmark on A100 on: schedule: - - cron: '00 17 * * *' # run at 5:00 PM UTC + - cron: '00 18 * * *' # run at 6:00 PM UTC, K8s containers will roll out at 12PM EST workflow_dispatch: inputs: userbenchmark_name: diff --git a/.github/workflows/v3-nightly.yml b/.github/workflows/v3-nightly.yml index d239f638a0..3b512693cc 100644 --- a/.github/workflows/v3-nightly.yml +++ b/.github/workflows/v3-nightly.yml @@ -2,7 +2,7 @@ name: TorchBench V3 nightly (A100) on: workflow_dispatch: schedule: - - cron: '00 17 * * *' # run at 5:00 PM UTC + - cron: '00 18 * * *' # run at 6:00 PM UTC, K8s containers will roll out at 12PM EST jobs: run-benchmark: