From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v2 0/7] Cleanup sched/process.c
Date: Mon, 13 Sep 2021 09:31:29 +0200 [thread overview]
Message-ID: <YT7+UU1d3llds9br@pevik> (raw)
In-Reply-To: <CAEemH2cO31kSwK3=tk6krB8ZZYPPaP+c-+5D7FGRK2ofYSmbtg@mail.gmail.com>
> > > But I just wondering, is there a run test file to perform this test case?
> > > I greped the runtest/* but find no file currently includes this:(.
> > IMHO it's in sched:
> > $ git grep -w process runtest/
> > runtest/sched:hackbench01 hackbench 50 process 1000
> Hmm, here "process" is only a parameter to hackbench01, it
> has no direct relevance to the process_stress/process.c.
> After checking the history a while, I think that process_stress/process.c
> is an independent test and obsoleted for a quite long time, maybe
> we can add online back to runtest/sched file or just let is there until
> someone converting to the new API.
> commit 576f1ee560b2370818b49366bad581952af3dd70
> Author: robbiew <robbiew>
> Date: Fri Feb 1 16:39:39 2002 +0000
> Removed a test that was not correctly running.
Ah, good catch! I didn't check it's not a binary which would be required.
I'll recheck it once again and send a patch to remove it then.
Kind regards,
Petr
WARNING: multiple messages have this Message-ID (diff)
From: Petr Vorel <pvorel@suse.cz>
To: Li Wang <liwang@redhat.com>
Cc: LTP List <ltp@lists.linux.it>
Subject: Re: [LTP] [PATCH v2 0/7] Cleanup sched/process.c
Date: Mon, 13 Sep 2021 09:31:29 +0200 [thread overview]
Message-ID: <YT7+UU1d3llds9br@pevik> (raw)
Message-ID: <20210913073129.Hgh6pP8guJa_9fmX_J-hfc6McdWxPPVR91lirSdbM8M@z> (raw)
In-Reply-To: <CAEemH2cO31kSwK3=tk6krB8ZZYPPaP+c-+5D7FGRK2ofYSmbtg@mail.gmail.com>
> > > But I just wondering, is there a run test file to perform this test case?
> > > I greped the runtest/* but find no file currently includes this:(.
> > IMHO it's in sched:
> > $ git grep -w process runtest/
> > runtest/sched:hackbench01 hackbench 50 process 1000
> Hmm, here "process" is only a parameter to hackbench01, it
> has no direct relevance to the process_stress/process.c.
> After checking the history a while, I think that process_stress/process.c
> is an independent test and obsoleted for a quite long time, maybe
> we can add online back to runtest/sched file or just let is there until
> someone converting to the new API.
> commit 576f1ee560b2370818b49366bad581952af3dd70
> Author: robbiew <robbiew>
> Date: Fri Feb 1 16:39:39 2002 +0000
> Removed a test that was not correctly running.
Ah, good catch! I didn't check it's not a binary which would be required.
I'll recheck it once again and send a patch to remove it then.
Kind regards,
Petr
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2021-09-13 7:31 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-10 13:08 [LTP] [PATCH v2 0/7] Cleanup sched/process.c Petr Vorel
2021-09-10 13:08 ` Petr Vorel
2021-09-10 13:08 ` [LTP] [PATCH v2 1/7] sched/process.c: Replace errfp with stderr Petr Vorel
2021-09-10 13:08 ` Petr Vorel
2021-09-10 13:08 ` [LTP] [PATCH v2 2/7] sched/process.c: Open debugfp with freopen() Petr Vorel
2021-09-10 13:08 ` Petr Vorel
2021-09-10 13:08 ` [LTP] [PATCH v2 3/7] ci/alpine: Enable process.c Petr Vorel
2021-09-10 13:08 ` Petr Vorel
2021-09-10 13:08 ` [LTP] [PATCH v2 4/7] sched/process.c: Log into cwd, add *.log suffix Petr Vorel
2021-09-10 13:08 ` Petr Vorel
2021-09-10 13:08 ` [LTP] [PATCH v2 5/7] sched/.gitignore: Ignore logs Petr Vorel
2021-09-10 13:08 ` Petr Vorel
2021-09-10 13:08 ` [LTP] [PATCH v2 6/7] sched/process.c: Remove non-Linux code Petr Vorel
2021-09-10 13:08 ` Petr Vorel
2021-09-10 13:08 ` [LTP] [PATCH v2 7/7] sched/process.c: Remove useless TRUE FALSE definitions Petr Vorel
2021-09-10 13:08 ` Petr Vorel
2021-09-13 6:04 ` [LTP] [PATCH v2 0/7] Cleanup sched/process.c Li Wang
2021-09-13 6:04 ` Li Wang
2021-09-13 6:32 ` Petr Vorel
2021-09-13 6:32 ` Petr Vorel
2021-09-13 7:26 ` Li Wang
2021-09-13 7:26 ` Li Wang
2021-09-13 7:31 ` Petr Vorel [this message]
2021-09-13 7:31 ` Petr Vorel
2021-09-13 7:33 ` Li Wang
2021-09-13 7:33 ` Li Wang
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=YT7+UU1d3llds9br@pevik \
--to=pvorel@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.