Milas Bowman 36bf0c458b chore(e2e): fix flaky cascade failure test
This was racy with the sleep, so the Compose file has been
tweaked to make it pass reliably.

Now, there's 3 services:
 * `running` - sleeps forever
 * `exit` - exits _successfully_ immediately
   * depends on `running` started
 * `fail` - exits _with error_ immediately
   * depends on `exit` succeeding

Now, the test can ensure that the containers are all run/
started in the expected order the assertions will be reliable.

Before, it was possible for `fail` to run & exit before `exit`,
for example. The `running` service also ensures there's always
at least one other "running" container when we do an abort.

Signed-off-by: Milas Bowman <milas.bowman@docker.com>
2024-04-24 11:03:27 +02:00
..
2024-03-22 11:21:14 +01:00
2023-11-27 14:19:53 +01:00
2024-03-22 14:33:56 +01:00
2023-11-24 10:46:33 +01:00
2023-12-05 18:54:31 +01:00
2023-12-05 18:54:31 +01:00
2024-04-09 15:30:42 +02:00