From 6e46d19063f9f96cd8e913f4f93437bfbfd1c731 Mon Sep 17 00:00:00 2001 From: Fabrizio Pezzino <79222190+fpezzinosn@users.noreply.github.com> Date: Tue, 9 Jul 2024 17:33:43 -0400 Subject: [PATCH] Reference only the runner name [OI-1830] (#1416) # Description @swift-nav/devinfra The Benchamarks Action has been failing since June 18th. The last [successful run](https://github.com/swift-nav/libsbp/actions/runs/9542331732) of Benchmarks contains the following warning ``` Found multiple labels in this runner. Support for multiple labels on Larger Runners will be removed after June 17th, 2024. Please visit changelog for the brownouts and more details: https://github.blog/changelog/2024-05-16-new-dates-for-actions-larger-runner-multi-label-deprecation/. ``` [Later runs](https://github.com/swift-nav/libsbp/actions/runs/9573895846) start showing that no runners are picking up the job. In this PR I'm changing the use of labels and instead only using the runner name. I have obtained that info from [here](https://github.com/swift-nav/libsbp/actions/runners). # API compatibility Does this change introduce a API compatibility risk? No, it only updates a github workflow file ## API compatibility plan If the above is "Yes", please detail the compatibility (or migration) plan: # JIRA Reference https://swift-nav.atlassian.net/browse/OI-1830 --- .github/workflows/benchmark.yaml | 2 +- rust/Dockerfile | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/.github/workflows/benchmark.yaml b/.github/workflows/benchmark.yaml index b05ebcc60..01a7e68ea 100644 --- a/.github/workflows/benchmark.yaml +++ b/.github/workflows/benchmark.yaml @@ -21,7 +21,7 @@ on: jobs: benchmark: name: Benchmark - runs-on: [linux, xlarge] + runs-on: [xlarge] steps: - uses: actions/checkout@v2 - name: Setup diff --git a/rust/Dockerfile b/rust/Dockerfile index 5c668148d..eaa556d0c 100644 --- a/rust/Dockerfile +++ b/rust/Dockerfile @@ -1,4 +1,4 @@ -FROM rust:1.65-slim-buster +FROM rust:1.67.1-slim-buster ARG DEBIAN_FRONTEND=noninterative