From: Cyril Hrubis <chrubis@suse.cz>
To: Bogdan Lezhepekov <bogdan.lezhepekov@suse.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v1 2/6] rt:pi-tests::sbrk_mutex: return actual exit code
Date: Fri, 24 Sep 2021 17:33:04 +0200 [thread overview]
Message-ID: <YU3vsBX0DEwSdOo9@yuki> (raw)
In-Reply-To: <20210914170851.22931-2-bogdan.lezhepekov@suse.com>
Hi!
I'm looking on how the pi-tests are supposed to be executed and it seems
that the return value does not seems to matter at all.
Each of these tests is executed by run_c_files.sh script that writes the
output into a logfile then a python script is used to parse the logfile.
I think that if we want to fix the realtime tests we should simplify
this mess first.
--
Cyril Hrubis
chrubis@suse.cz
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2021-09-24 15:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-14 17:08 [LTP] [PATCH v1 1/6] realtime:async_handler_jk: return actual exit code Bogdan Lezhepekov
2021-09-14 17:08 ` Bogdan Lezhepekov via ltp
2021-09-14 17:08 ` [LTP] [PATCH v1 2/6] rt:pi-tests::sbrk_mutex: " Bogdan Lezhepekov
2021-09-14 17:08 ` Bogdan Lezhepekov via ltp
2021-09-24 15:33 ` Cyril Hrubis [this message]
2021-09-14 17:08 ` [LTP] [PATCH v1 3/6] rt:pi-tests:testpi-0: " Bogdan Lezhepekov
2021-09-14 17:08 ` Bogdan Lezhepekov via ltp
2021-09-14 17:08 ` [LTP] [PATCH v1 4/6] rt:pi-tests:test-skeleton: fix wrong return value Bogdan Lezhepekov
2021-09-14 17:08 ` Bogdan Lezhepekov via ltp
2021-09-14 17:08 ` [LTP] [PATCH v1 5/6] rt:pi-tests:testpi-5: return exit code Bogdan Lezhepekov
2021-09-14 17:08 ` Bogdan Lezhepekov via ltp
2021-09-24 9:53 ` Petr Vorel
2021-09-24 10:07 ` Bogdan Lezhepekov via ltp
2021-09-14 17:08 ` [LTP] [PATCH v1 6/6] rt:pi-tests:testpi-6: " Bogdan Lezhepekov
2021-09-14 17:08 ` Bogdan Lezhepekov via ltp
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=YU3vsBX0DEwSdOo9@yuki \
--to=chrubis@suse.cz \
--cc=bogdan.lezhepekov@suse.com \
--cc=ltp@lists.linux.it \
/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