From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Simone Weiß" <simone.p.weiss@posteo.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] patchtest: Add further information for failed testcases
Date: Thu, 15 Feb 2024 22:10:22 +0000 [thread overview]
Message-ID: <ccccce2389cda121cfc5cef4c87b7edf63d6a41b.camel@linuxfoundation.org> (raw)
In-Reply-To: <20240215213932.245929-1-simone.p.weiss@posteo.com>
On Thu, 2024-02-15 at 21:39 +0000, Simone Weiß wrote:
> From: Simone Weiß <simone.p.weiss@posteo.com>
>
> Add more information to log messages when a test case fails.
> Still keep it short and mostly reference the documentation. Reasson is that
> documentation should already contain the needed information, do not duplicate
> it here, so we also do not need to update here should the doc/policy change.
>
> Signed-off-by: Simone Weiß <simone.p.weiss@posteo.com>
This does get a little tricky since the responses from patchtest on our
test infrastructure has a character limit for security reasons.
I have wondered if we do need to change it to some kind of code
response which can then be translated back into real text.
The reason for the character limit is to stop abuse of the VMs that run
the tests, you can't mine bitcoin and pass them out as the failure
message for example.
Cheers,
Richard
next prev parent reply other threads:[~2024-02-15 22:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-15 21:39 [PATCH] patchtest: Add further information for failed testcases simone.p.weiss
2024-02-15 22:10 ` Richard Purdie [this message]
2024-02-16 16:19 ` [OE-core] " Simone Weiß
2024-02-16 16:43 ` Trevor Gamblin
2024-02-16 16:51 ` Richard Purdie
2024-02-16 20:26 ` Simone Weiß
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=ccccce2389cda121cfc5cef4c87b7edf63d6a41b.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=simone.p.weiss@posteo.com \
/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