balena-supervisor/test/unit
Christina W 71d24d6e33 Parse container exit error message instead of status
The previous implementation in #2170 of parsing the container status was too general,
because it relied on the mistaken assumption that a container would have a status of
`Stopped` if it was manually stopped. This turned out to be untrue, as manually stopped
containers were also getting restarted by the Supervisor due to their inspect status of
`exited`. With this, parsing the exit message became unavoidable as there are no other
clear ways to discern a container that has been manually stopped and shouldn't be started
from a container experiencing the Engine-host race condition issue (again, see #2170).

Since we're just parsing the exit error message, we don't need to worry about different behaviors
amongst restart policies, as any container with the error message on exit should be started.

Change-type: patch
Closes: #2178
Signed-off-by: Christina Ying Wang <christina@balena.io>
2023-06-22 14:43:17 -07:00
..
compose Parse container exit error message instead of status 2023-06-22 14:43:17 -07:00
config Migrate all device config tests to integration. 2022-11-14 11:12:52 -03:00
device-api Update host-config, route, and action tests for host config endpoints 2023-01-11 15:48:13 -08:00
lib Fix sw.arch typo when testing contracts 2023-05-11 13:07:26 -04:00
.mocharc.js Disable logs globally using mocha hooks 2022-09-28 10:37:41 -03:00
network.spec.ts Migrate simple legacy tests to test/unit and test/integration 2022-10-18 20:36:53 -03:00
types.spec.ts Fix withDefault type helper to work with boolean 2022-09-13 20:08:32 +00:00