Michael BolinandCodex 86d1bd8f63 bazel: add explicit rust test shard labels ...

Generate separate Bazel test labels for selected large Rust test targets so BuildBuddy can report timing and flakiness per shard. Keep the original aggregate target names as test_suites over the generated shard targets.

For integration tests, compile one manual *-all-test-bin rust_test and make each shard label a lightweight wrapper around that binary. This preserves distinct BuildBuddy labels without compiling the same test crate once per shard.

Patch the pinned rules_rust archive with the stable name-hash sharding, explicit RULES_RUST_TEST_* env support, Windows manifest fallback, and Windows-safe PowerShell UInt32 masking from hermeticbuild/rules_rust#14 until Codex can bump to a merged rules_rust commit that contains it.

Co-authored-by: Codex <noreply@openai.com>

2026-04-15 16:24:57 -07:00

..

frames

Rename tui_app_server to tui (#16104)

2026-03-28 11:23:07 -06:00

src

Re-enable it (#18002)

2026-04-15 22:09:41 +01:00

tests

[codex] reduce module visibility (#16978)

2026-04-07 08:03:35 -07:00

BUILD.bazel

bazel: add explicit rust test shard labels

2026-04-15 16:24:57 -07:00

Cargo.toml

TUI: enforce core boundary (#17399)

2026-04-10 20:25:31 -07:00

prompt_for_init_command.md

Rename tui_app_server to tui (#16104)

2026-03-28 11:23:07 -06:00

styles.md

Rename tui_app_server to tui (#16104)

2026-03-28 11:23:07 -06:00

tooltips.txt

feat(tui): Ctrl+O copy hotkey and harden copy-as-markdown behavior (#16966)

2026-04-09 18:10:38 -03:00