From: Jan Kiszka <jan.kiszka@siemens.com>
To: Florian Bezdeka <florian.bezdeka@siemens.com>, xenomai@lists.linux.dev
Subject: Re: [xenomai-images][PATCH 0/2] Fix pipeline failure detection
Date: Thu, 23 Feb 2023 18:54:42 +0100 [thread overview]
Message-ID: <64692286-6986-4954-c297-550b154f5910@siemens.com> (raw)
In-Reply-To: <20230223074047.3974956-1-florian.bezdeka@siemens.com>
On 23.02.23 08:40, Florian Bezdeka wrote:
> Hi,
>
> a failing xenomai (smokey) test was not properly reported by gitlab-ci.
> In addition some bitbake warnings were triggered by the option file used
> for CI builds.
>
> It seems that LAVA decided to report test failures now as "failures"
> instead of "errors". I did some research but could not identify any
> recent LAVA change that triggers this. Might be the case that I
> overlooked something or the error detection has been broken for a long
> time now.
>
> I have one more patch pending: Enable compat testing for the stable
> 3.2.x branch. Let me know if that is of general interest. It helped to
> detect and fix some compat issues for this branch.
>
> Best regards,
> Florian
>
> Florian Bezdeka (2):
> ci: Fix handling of lava test failures
> ci: Fix some bitbake warnings triggered by opt-ci.yml
>
> opt-ci.yml | 4 ++--
> scripts/run-lava-tests.sh | 17 +++++++++++++----
> 2 files changed, 15 insertions(+), 6 deletions(-)
>
Thanks, applied.
Jan
--
Siemens AG, Technology
Competence Center Embedded Linux
prev parent reply other threads:[~2023-02-23 17:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-23 7:40 [xenomai-images][PATCH 0/2] Fix pipeline failure detection Florian Bezdeka
2023-02-23 7:40 ` [xenomai-images][PATCH 1/2] ci: Fix handling of lava test failures Florian Bezdeka
2023-02-23 7:40 ` [xenomai-images][PATCH 2/2] ci: Fix some bitbake warnings triggered by opt-ci.yml Florian Bezdeka
2023-02-23 17:54 ` Jan Kiszka [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=64692286-6986-4954-c297-550b154f5910@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=florian.bezdeka@siemens.com \
--cc=xenomai@lists.linux.dev \
/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;
as well as URLs for NNTP newsgroup(s).