Go: gdi

e2e-gdi is a deliberate placeholder that exits non-zero, so a GDI run can never be read as a pass.

1. Select the distribution

   E2E_SUITE=go E2E_ENV=gdi ./dev.sh start

   E2E_SUITE=go is the default and can be omitted.

2. Expect failure

   The binary prints e2e-gdi: the GDI pipeline is not implemented to stderr and exits 1.

why does it fail on purpose?

Nothing about a GDI run should be readable as a pass while no GDI pipeline exists. Exiting non-zero with an explicit message means a scheduled or scripted run surfaces the gap instead of hiding it.

how is this different from the JUnit GDI distribution?

The retiring JUnit GDI class reports seven passing tests with empty bodies, a false green; this binary exits non-zero precisely so it cannot produce one. Neither runner has GDI coverage; only this one says so.

why is there more than one selector?

E2E_SUITE picks the runner (go or java) and E2E_ENV picks which Go binary runs, so the pair selects one of the six distributions. The retiring JUnit runner uses its own E2E_TESTS_INTEGRATION selector instead and ignores E2E_ENV. Neither runner selects an environment at runtime: choosing the environment is choosing the program.