Slow CI runners

Open
  • Is something wrong?
#74 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
18/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Active
Tech stack
github-actions
Domain
ci-cd

Research direction

The payload names no file or test; the only pointer is a failing GitHub Actions run linked in the body. Start by reading the workflow definitions under .github/workflows and checking which runner labels the slow job requests. The issue does not say what the fix should be, so a newcomer would first need a maintainer to confirm whether the problem is runner capacity or job configuration.

Written by the indexing model from the issue text.

Description

There seems to be something wrong with the CI runners in this project. For example:

This check has been waiting 30 mins for a runner to pick it up and execute it. I'd expect this process to be instance, and that the only wait time is just the CI run itself.

Dominant language
Rust
Stars
30
Forks
30
Avg merge
3d 19h
Merged PRs (30d)
15

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from apache/datafusion-iceberg

All issues in apache/datafusion-iceberg

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.