Skip to content

[9.0.2] Make include verification aware of Windows case-insensitivity#29214

Merged
iancha1992 merged 2 commits intobazelbuild:release-9.0.2from
iancha1992:cp246ea9891e_2
Apr 2, 2026
Merged

[9.0.2] Make include verification aware of Windows case-insensitivity#29214
iancha1992 merged 2 commits intobazelbuild:release-9.0.2from
iancha1992:cp246ea9891e_2

Conversation

@iancha1992
Copy link
Copy Markdown
Member

Description

Motivation

Build API Changes

No

Checklist

  • I have added tests for the new use cases (if any).
  • I have updated the documentation (if applicable).

Release Notes

RELNOTES: None

Commit 79fb843 and 246ea98

fmeum added 2 commits April 2, 2026 15:15
The execution OS is determined by the specified test exec group, which can differ from the `test` exec group as well as the test rule's default execution group. Also renames some helper methods to make this class of bugs less likely and clean up `ConstraintConstants` to support the `macos` alias for the `darwin` OS constraint value.

As a consequence of this refactoring, it became clear that the shell path was determined by the host OS when the execution OS is Linux or macOS, resulting in a Windows host trying to use the Windows shell path when running e.g. a genrule on Linux. In a surprising turn of events, this behavior is what holds Bazel's own Java integration tests together on Windows - for now. As a result, the fix is accompanied by a manual override on `--shell_executable` in `BuildIntegrationTest` for a Windows host.

Closes bazelbuild#28038.

PiperOrigin-RevId: 874626714
Change-Id: Icae167c5e58309258b3c73bac99796a512d2f26d
…uild#28810)

### Description

### Motivation
Fix bazelbuild#28803

### Build API Changes

No

### Checklist

- [ ] I have added tests for the new use cases (if any).
- [ ] I have updated the documentation (if applicable).

### Release Notes

RELNOTES: None

Closes bazelbuild#28810.

PiperOrigin-RevId: 893719641
Change-Id: I4cd7a5ac6b1a35467ea38fdfd1063dc3ed35ffa0
@iancha1992 iancha1992 added team-Rules-CPP Issues for C++ rules awaiting-review PR is awaiting review from an assigned reviewer labels Apr 2, 2026
@iancha1992 iancha1992 marked this pull request as ready for review April 2, 2026 22:17
@iancha1992 iancha1992 requested a review from a team as a code owner April 2, 2026 22:17
@github-actions github-actions Bot added team-Performance Issues for Performance teams team-Configurability platforms, toolchains, cquery, select(), config transitions team-Remote-Exec Issues and PRs for the Execution (Remote) team team-Starlark-Integration Issues involving Bazel's integration with Starlark, excluding builtin symbols labels Apr 2, 2026
@iancha1992
Copy link
Copy Markdown
Member Author

iancha1992 commented Apr 2, 2026

This contains two commits 79fb843 and 246ea98 because there was a merge conflict. Are you okay with it? @Wyverald @meteorcloudy @trybka @pzembrod @lberki @fmeum

@iancha1992 iancha1992 enabled auto-merge April 2, 2026 22:18
@iancha1992 iancha1992 added this pull request to the merge queue Apr 2, 2026
Merged via the queue into bazelbuild:release-9.0.2 with commit 8d6a1c7 Apr 2, 2026
47 checks passed
@github-actions github-actions Bot removed the awaiting-review PR is awaiting review from an assigned reviewer label Apr 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

team-Configurability platforms, toolchains, cquery, select(), config transitions team-Performance Issues for Performance teams team-Remote-Exec Issues and PRs for the Execution (Remote) team team-Rules-CPP Issues for C++ rules team-Starlark-Integration Issues involving Bazel's integration with Starlark, excluding builtin symbols

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants