From: Peter Korsgaard <peter@korsgaard.com>
To: Romain Naour <romain.naour@smile.fr>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] support/misc/gitlab-ci.yml.in: print error log if the runtime test fail
Date: Sun, 03 Dec 2023 20:21:18 +0100 [thread overview]
Message-ID: <87plznw0r5.fsf@48ers.dk> (raw)
In-Reply-To: <20231111113731.859747-1-romain.naour@smile.fr> (Romain Naour's message of "Sat, 11 Nov 2023 12:37:31 +0100")
>>>>> "Romain" == Romain Naour <romain.naour@smile.fr> writes:
> When an error occurs, the gitlab-ci job log doesn't contain any useful
> information than the name of the failing test:
> FAIL: test_run (tests.package.test_python_paho_mqtt.TestPythonPahoMQTT)
> In order to encourage contributors to investigate issues reported by
> gitlab-ci, we want to print the last lines of the log file (build or
> runtime).
> Unfortunately, gitlab-ci job log completely strips lines ending with
> CRCRLF [1][2]. We have to take a look at the gitlab-ci raw log to see
> the complete log [3].
> To workaround this issue, remove crlf from qemu serial stdio log
> while printing in the gitlab-ci job log (we don't want to change
> the log file generated by support/testing/run-tests and saved as
> artefacts).
> [1] https://gitlab.com/gitlab-org/gitlab/-/issues/218771
> [2] https://gitlab.com/kubu93/buildroot/-/jobs/5492937691
> [3] https://gitlab.com/kubu93/buildroot/-/jobs/5492937691/raw
> Cc: Peter Korsgaard <peter@korsgaard.com>
> Signed-off-by: Romain Naour <romain.naour@smile.fr>
Committed to next, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2023-12-03 19:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-11 11:37 [Buildroot] [PATCH] support/misc/gitlab-ci.yml.in: print error log if the runtime test fail Romain Naour
2023-12-03 19:21 ` Peter Korsgaard [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87plznw0r5.fsf@48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=romain.naour@smile.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox