If that's correct, then it would mean we run all e2e tests twice, but only for a single test; we can cut the number of checks in half if we don't do so;
Always enable experimental on the daemon (we already do so!)
Run the tests and let the "experimental" one be skipped
Description
While working on https://github.com/docker/cli/pull/5139, I noticed that CI was green even if we didn't enable experimental on the daemon.
I was curious how the
experimental
andnon-experimental
e2e tests differed, and after a cursory glance, it may be only for a single test; https://github.com/docker/cli/blob/591bd174241555b26fb5e92de5d7a9da094523c1/e2e/image/build_test.go#L128If that's correct, then it would mean we run all e2e tests twice, but only for a single test; we can cut the number of checks in half if we don't do so;
experimental
on the daemon (we already do so!)