From 2a644b5397360ae777c813e4a1f6b09331e033a6 Mon Sep 17 00:00:00 2001 From: Felix Marty Date: Mon, 20 Nov 2023 10:18:34 +0000 Subject: [PATCH] is concurrency the reason for cancelled job? --- .github/workflows/build.yaml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/.github/workflows/build.yaml b/.github/workflows/build.yaml index 94675011..99abd352 100644 --- a/.github/workflows/build.yaml +++ b/.github/workflows/build.yaml @@ -147,9 +147,9 @@ jobs: cache-to: type=registry,ref=registry.internal.huggingface.tech/api-inference/community/text-generation-inference:cache,mode=min build-and-push-image-rocm: - concurrency: - group: ${{ github.workflow }}-${{ github.job }}-${{ github.head_ref || github.run_id }} - cancel-in-progress: true + #concurrency: + # group: ${{ github.workflow }}-${{ github.job }}-${{ github.head_ref || github.run_id }} + # cancel-in-progress: true needs: start-runner # required to start the main job when the runner is ready runs-on: ${{ needs.start-runner.outputs.label }} # run the job on the newly created runner permissions: