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

..

advent2024

Add advent of code 2024 day 14 and day 15 part 1 solutions (#6597)

2026-01-14 18:33:23 +00:00

bazel

Test that the built toolchain works with the example Bazel project (#6653)

2026-01-29 02:14:17 +00:00

interop/cpp

Clean up after combination of #6634 and #6635. (#6640)

2026-01-21 21:03:35 +00:00

re2_playground

Add line editor to RE2 example. (#6337)

2025-11-10 23:53:23 +00:00

bazel_test_runner.py

Test that the built toolchain works with the example Bazel project (#6653)

2026-01-29 02:14:17 +00:00

BUILD

Test that the built toolchain works with the example Bazel project (#6653)

2026-01-29 02:14:17 +00:00

hello_world.carbon

Add Core.PrintStr and a "hello world" example (#6493)

2025-12-12 20:07:05 +00:00

sieve.carbon

Remove support for addr (#6375)

2025-11-18 19:48:58 +00:00