From: Petr Vorel <pvorel@suse.cz>
To: Cyril Hrubis <chrubis@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH] cpuset_memory_testset.sh: Give SIGUSR1 handler time to run before changing target mapping node in tests 12 and 13
Date: Tue, 1 Apr 2025 09:20:06 +0200 [thread overview]
Message-ID: <20250401072006.GB299271@pevik> (raw)
In-Reply-To: <Z9lTTX4BrkpFhmQV@yuki.lan>
Hi all,
> Hi!
> > Fixes: 70259d6e7
> > Signed-off-by: Jacob Martin <jacob.martin@canonical.com>
> > ---
> > .../cpuset/cpuset_memory_test/cpuset_memory_testset.sh | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> > diff --git a/testcases/kernel/controllers/cpuset/cpuset_memory_test/cpuset_memory_testset.sh b/testcases/kernel/controllers/cpuset/cpuset_memory_test/cpuset_memory_testset.sh
> > index c1e7cea8f..04d7cc877 100755
> > --- a/testcases/kernel/controllers/cpuset/cpuset_memory_test/cpuset_memory_testset.sh
> > +++ b/testcases/kernel/controllers/cpuset/cpuset_memory_test/cpuset_memory_testset.sh
> > @@ -383,7 +383,7 @@ talk2memory_test_for_case_12_13()
> > sleep 1
> > echo $1 > "$2/tasks"
> > /bin/kill -s SIGUSR1 $1
> > -
> > + sleep 1
> This is just another workaround that does not fix the real issue and
> that is that the C child does not communicate properly with the shell
> code. The best solution here would be to rewrite these tests into C.
> There is not that much work the shell does and we would avoid parsing
> files written by the C helper in the shell as well.
@Jacob FYI how looks the patchset which rewrites test6 to C:
https://patchwork.ozlabs.org/project/ltp/list/?series=450626&state=*
Feel free to pick another test.
Kind regards,
Petr
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2025-04-01 7:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-07 22:58 [LTP] [PATCH] cpuset_memory_testset.sh: Give SIGUSR1 handler time to run before changing target mapping node in tests 12 and 13 Jacob Martin
2025-03-18 11:04 ` Cyril Hrubis
2025-04-01 7:20 ` Petr Vorel [this message]
2025-04-01 18:27 ` Jacob Martin
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=20250401072006.GB299271@pevik \
--to=pvorel@suse.cz \
--cc=chrubis@suse.cz \
--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 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.