bazelbuild / bazelbuild/continuous-integration

Unexpected failures on windows runners

Open
#1,201 16 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
302
Forks
194
Avg merge
1d 19h
Merged PRs (30d)
41

Description

Initially noticed on https://github.com/bazelbuild/rules_rust/pull/879#issuecomment-894896993

Did something change about the windows runners recently? As you can see in that comment, build [4029](https://buildkite.com/bazel/rules-rust-rustlang/builds/4029) succeeded but build [4046](https://buildkite.com/bazel/rules-rust-rustlang/builds/4046#73d9f1e8-780c-4833-bb42-85b1c29c1fa8) failed when no changes had been made to that branch.

Contributor guide

Open the contributing guide

Research direction

Start with the linked pull-request comment and compare Buildkite builds 4029 and 4046, focusing on the Windows runner details shown there. Trace what changed between the successful and failed runs; done means identifying the runner-related cause and documenting or restoring the expected CI behavior.

Written by the indexing model from the issue text.

Assessment

Domain
ci-cd, devops, infrastructure
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.