Skip to content

Commit

Permalink
Reference only the runner name [OI-1830] (#1416)
Browse files Browse the repository at this point in the history
# 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:

<!-- Provide a short explanation plan here -->

# JIRA Reference

https://swift-nav.atlassian.net/browse/OI-1830
  • Loading branch information
fpezzinosn committed Jul 9, 2024
1 parent 991f042 commit 6e46d19
Show file tree
Hide file tree
Showing 2 changed files with 2 additions and 2 deletions.
2 changes: 1 addition & 1 deletion .github/workflows/benchmark.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,7 @@ on:
jobs:
benchmark:
name: Benchmark
runs-on: [linux, xlarge]
runs-on: [xlarge]
steps:
- uses: actions/checkout@v2
- name: Setup
Expand Down
2 changes: 1 addition & 1 deletion rust/Dockerfile
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
FROM rust:1.65-slim-buster
FROM rust:1.67.1-slim-buster

ARG DEBIAN_FRONTEND=noninterative

Expand Down

0 comments on commit 6e46d19

Please sign in to comment.