apache / apache/arrow-rs

MIRI jobs consume a lot of GH runner action time

Open
#11,045 3 comments 0 reactions 0 assignees View on GitHub
bug
Dominant language
Rust
Stars
3.6k
Forks
1.3k
Avg merge
2d 18h
Merged PRs (30d)
169

Description

### Describe the bug

The Infra Report (needs a login, not sure how many people can see this)
https://infra-reports.apache.org/#ghactions&project=arrow&hours=168&limit=15&group=name

Image

Shows that our MIRI job is consuming 16% of the total GH action usage for the Arrow project -- this is across all language implementations.

This seems like a large amount of time / cost to devote to a job compared to its relative benefit.

### To Reproduce

Do nothing

### Expected behavior

It would be nice to reduce the cost of running the MIRI tests

Perhaps we could change the job so it:
1. does not run by default on all PRs / pushes (only run on commits to main)
2. can be run manually on particular PRs if needed

### Additional context

_No response_

Contributor guide

Open the contributing guide

Research direction

Start by locating the GitHub Actions workflow that defines the MIRI job and inspect its current triggers and runtime. Compare the available trigger options with the issue's proposed main-branch and manual-run behavior, then verify that the resulting workflow no longer runs unnecessarily on all PRs or pushes while remaining runnable when needed.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions, rust
Domain
ci-cd, devops
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
68/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.