From: simone.p.weiss@posteo.com
To: openembedded-core@lists.openembedded.org
Cc: "Simone Weiß" <simone.p.weiss@posteo.com>
Subject: [PATCH v2] patchtest: provide further guidance for failed testcases
Date: Fri, 23 Feb 2024 20:17:45 +0000 [thread overview]
Message-ID: <20240223201745.16234-1-simone.p.weiss@posteo.com> (raw)
From: Simone Weiß <simone.p.weiss@posteo.com>
Cross-reference the wiki page on patchtest now that it is updated and contains
more information how to address failed testcases. Adding it in patchtest only
is enough as patchtest-send-result already points to the wikipage for failures.
Signed-off-by: Simone Weiß <simone.p.weiss@posteo.com>
---
v2: Instead of prodvidng the infos in the log point to the now updated wiki to
avoid issues with autobuilder when adding more lines.
scripts/patchtest | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/scripts/patchtest b/scripts/patchtest
index 3163420220..42e70fd4b7 100755
--- a/scripts/patchtest
+++ b/scripts/patchtest
@@ -164,9 +164,9 @@ def run(patch, logfile=None):
if premerge_result == 2 and postmerge_result == 2:
logger.error('patchtest: No test cases found - did you specify the correct suite directory?')
if premerge_result == 1 or postmerge_result == 1:
- logger.error('WARNING: patchtest: At least one patchtest caused a failure or an error - please check')
+ logger.error('WARNING: patchtest: At least one patchtest caused a failure or an error - please check https://wiki.yoctoproject.org/wiki/Patchtest for further guidance for further guidance')
else:
- logger.error('OK: patchtest: All patchtests passed')
+ logger.info('OK: patchtest: All patchtests passed')
print('----------------------------------------------------------------------\n')
return premerge_result or postmerge_result
--
2.39.2
next reply other threads:[~2024-02-23 20:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-23 20:17 simone.p.weiss [this message]
2024-02-23 20:30 ` [OE-core] [PATCH v2] patchtest: provide further guidance for failed testcases Trevor Gamblin
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=20240223201745.16234-1-simone.p.weiss@posteo.com \
--to=simone.p.weiss@posteo.com \
--cc=openembedded-core@lists.openembedded.org \
/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