2 Commits

Include renames

Author	SHA1	Message	Date
Jon Ross-PerkinsandChandler Carruth	17897bb05d	Add transient error retries to bazel integration tests (#6796) ... e.g. for failures like https://github.com/carbon-language/carbon-lang/actions/runs/22418738440/job/64911093548 We work around this similarly in run_bazel.py already; this is mirroring over some of the logic (sharing would require work on Python's set up). Assisted-by: Google Antigravity with Gemini 3 Flash --------- Co-authored-by: Chandler Carruth <chandlerc@gmail.com>	2026-02-26 17:36:51 +00:00
Chandler Carruth	529dcfcfec	Test that the built toolchain works with the example Bazel project (#6653) ... I wasn't sure I'd be able to really test this code path, but then I remembered that Bazel has a whole platform for running Bazel from within an integration test, and it turns out to work brilliantly. It even lets us point the child Bazel invocations to the just-built toolchain. This should both give us confidence that we don't accidentally hit a Bazel incompatibility with the example project, and it should ensure that if something about the installed toolchain would stop being compatible with building via Bazel we'll catch it early. The tests are integration tests and so a bit slow: 15s or so. But `//examples/...` is already pretty expensive and no other testing patterns are impacted.	2026-01-29 02:14:17 +00:00