sqlite: exit code: allow -1

The value of -1 is used when we do not _yet_ know the exit code of the
container.  Otherwise, the DB checks would error.  There's probably a
smarter than allowing -1 but for now, that will do the trick and let the
tests progress.

Signed-off-by: Valentin Rothberg <vrothberg@redhat.com>

libpod/sqlite_state.go

@@ -856,7 +856,7 @@ func (s *SQLiteState) AddContainerExitCode(id string, exitCode int32) (defErr er
 	}()
 
 	if _, err := tx.Exec("INSERT INTO ContainerExitCode VALUES (?, ?, ?);", id, time.Now().Unix(), exitCode); err != nil {
-		return fmt.Errorf("adding container %s exit code: %w", id, err)
+		return fmt.Errorf("adding container %s exit code %d: %w", id, exitCode, err)
 	}
 
 	if err := tx.Commit(); err != nil {

libpod/sqlite_state_internal.go

@@ -86,7 +86,7 @@ func sqliteInitTables(conn *sql.DB) (defErr error) {
                 ExitCode INTEGER,
                 JSON     TEXT    NOT NULL,
                 FOREIGN KEY (ID) REFERENCES ContainerConfig(ID) DEFERRABLE INITIALLY DEFERRED,
-                CHECK (ExitCode BETWEEN 0 AND 255)
+                CHECK (ExitCode BETWEEN -1 AND 255)
         );`
 
 	const containerExecSession = `
@@ -120,7 +120,7 @@ func sqliteInitTables(conn *sql.DB) (defErr error) {
                 ID        TEXT    PRIMARY KEY NOT NULL,
                 Timestamp INTEGER NOT NULL,
                 ExitCode  INTEGER NOT NULL,
-                CHECK (ExitCode BETWEEN 0 AND 255)
+                CHECK (ExitCode BETWEEN -1 AND 255)
         );`
 
 	const podConfig = `