From: Cyril Hrubis <chrubis@suse.cz>
To: Martin Doucha <mdoucha@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH] Disable failure hints before we actually run the test
Date: Tue, 17 Sep 2024 17:50:25 +0200 [thread overview]
Message-ID: <ZumlQeDF2jk_4gOc@yuki.lan> (raw)
In-Reply-To: <fff1e0af-a137-4f3b-8cdc-e1fd3ff8795a@suse.cz>
Hi!
> does it make sense to print failure hints after setup() failure? I can
> think of a few cases where bug effects can be delayed until cleanup()
> but it seems a bit early to me to cover setup() as well. I think the
> flag could be moved to shared memory, enabled immediately before calling
> run_tests() and disabled immediately after handling child's exit status
> in fork_testrun().
My idea here was that we should always show the hints once we executed a
test function at least once. The rationale is that if the run_test()
corrupted kernel memory it may manifest at any point e.g. when we
attempt to setup a next loop device for the next filesytem (for
.all_filesystems).
So the idea is not to print them during the test library setup i.e.
do_setup() function but enable them right after that and keeping them
on.
--
Cyril Hrubis
chrubis@suse.cz
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2024-09-17 15:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-17 8:25 [LTP] [PATCH] Disable failure hints before we actually run the test Cyril Hrubis
2024-09-17 12:22 ` Andrea Cervesato via ltp
2024-09-17 12:23 ` Andrea Cervesato via ltp
2024-09-17 14:36 ` Martin Doucha
2024-09-17 15:50 ` Cyril Hrubis [this message]
2024-09-17 15:56 ` Martin Doucha
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=ZumlQeDF2jk_4gOc@yuki.lan \
--to=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
--cc=mdoucha@suse.cz \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.