From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] Convert chdir01 to the new API
Date: Fri, 24 Jul 2020 10:07:32 +0200 [thread overview]
Message-ID: <20200724080732.GA16478@yuki.lan> (raw)
In-Reply-To: <20200723113317.GA18525@dell5510>
Hi!
> > Honestly speak, I don't like merge chdir02 into chdir01 and we should
> > cleanup chdir02 case individually.
We usually tend to split test into possitive and negative testcases
in order to avoid overly complex code. In this case the code looks clean
enough though.
I guess that if we wanted to have a separate test for possitive tests,
we would do something more interesting. Maybe something that does
chdir() and getcwd() in a loop for a while for a random path from a set
of paths, e.g. $TMPDIR, /, "..", "." and would expect the getcwd() to
match the new path after successful chdir() and remain unchanged after
failure. It would probably even more interesting to run chdir() and
getcwd() in a loop in several different threads, in such case we would
expect a valid return from getcwd(), i.e. any of the paths we pass to
chdir().
> chdir02.c tests chdir("/"); and chdir("/tmp"). Not sure whether full path is
> more coverage than relative path from chdir01.c.
> If we consider these useful, we can just add it into chdir01.c.
>
> Although it looks a bit strange to chroot into root, I'd use just that and avoid
> /tmp (it breaks at least for Android with no good reason).
I guess that we can add /etc or something that is generally present on
the system.
--
Cyril Hrubis
chrubis@suse.cz
next prev parent reply other threads:[~2020-07-24 8:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-17 15:24 [LTP] [PATCH] Convert chdir01 to the new API Martin Doucha
2020-07-22 8:52 ` Yang Xu
2020-07-23 11:33 ` Petr Vorel
2020-07-24 8:07 ` Cyril Hrubis [this message]
2020-07-24 12:36 ` Petr Vorel
2020-07-24 12:47 ` Martin Doucha
2020-07-24 13:26 ` Cyril Hrubis
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=20200724080732.GA16478@yuki.lan \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox