f1106b9b causes build failures due to valid log lines

[efd6]

Since f1106b9 valid builds can fail with

Error: error running package system tests: could not complete test run: check log messages failed: malformed docker-compose log line

With judicious addition of information to the error message:

diff --git a/internal/stack/parselogs.go b/internal/stack/parselogs.go
index 6b8557e..a2d62b6 100644
--- a/internal/stack/parselogs.go
+++ b/internal/stack/parselogs.go
@@ -41,7 +41,7 @@ func ParseLogs(options ParseLogsOptions, process func(log LogLine) error) error
                messageSlice := strings.SplitN(line, "|", 2)

                if len(messageSlice) != 2 {
-                       return fmt.Errorf("malformed docker-compose log line")
+                       return fmt.Errorf("malformed docker-compose log line: %q", line)
                }

                messageLog := messageSlice[1]

we see

Error: error running package system tests: could not complete test run: check log messages failed: malformed docker-compose log line: "Attaching to elastic-package-stack_elastic-agent_1"

Replacing the error return with a continue allows completion of the assessment of log lines that appears to be the intention of #1256.

/cc @mrodm

[mrodm]

@efd6 What docker-compose version was used in those executions ? Maybe v1.x?
In CI we're using currently docker-compose v2

[efd6]

A bunch of people are seeing it. I am using v1, but I can't speak for others.

[ebeahan]

docker-compose v1.x is what installs alongside Docker Desktop on Mac: