All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Schmitt via Grub-devel <grub-devel@gnu.org>
To: grub-devel@gnu.org
Cc: Thomas Schmitt <scdbackup@gmx.net>, development@efficientek.com
Subject: Re: make check as superuser leaves empty directories in /-directory
Date: Wed, 24 Jul 2024 19:08:27 +0200	[thread overview]
Message-ID: <3054302259767843371@scdbackup.webframe.org> (raw)
In-Reply-To: <624730237155225624@scdbackup.webframe.org>

Hi,

with the freshly submitted patch applied, i see as superuser:

  # make check TESTS=grub_cmd_cryptomount
  ...
  PASS: grub_cmd_cryptomount
  ...
  # echo $?
  0
  #

No new directories appeared in the root directory. During the "make check"
run i could spot single files /tmp/*LUKS* which did not exist any more
soon after.

By help of Greg Wooledge on debian-user mailing i was able to find the
description of ${TMPDIR=/tmp} in man bash and man dash.
"=" sets the variable to /tmp only if TMPDIR is not set.
":=" sets also if it is set to empty text.

The use of TMPDIR in tests/ is mainly made safe by ${TMPDIR:-/tmp}, not
by ${TMPDIR-/tmp}. So i deem ${TMPDIR:=/tmp} the right thing to do,
if not every expansion of $TMPDIR shall be made safe individually.

If the gnulib tests are run by "make check", then one should review
the use of ${TMPDIR=/tmp} in
  ./gnulib/tests/test-copy-acl.sh
  ./gnulib/tests/test-file-has-acl.sh
  ./gnulib/tests/test-set-mode-acl.sh
  ./gnulib/tests/test-copy-file.sh
  ./gnulib/tests/test-parse-duration.sh


Have a nice day :)

Thomas


_______________________________________________
Grub-devel mailing list
Grub-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/grub-devel

      reply	other threads:[~2024-07-24 17:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-24 10:31 make check as superuser leaves empty directories in /-directory Thomas Schmitt via Grub-devel
2024-07-24 12:55 ` Thomas Schmitt via Grub-devel
2024-07-24 17:08   ` Thomas Schmitt via Grub-devel [this message]

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=3054302259767843371@scdbackup.webframe.org \
    --to=grub-devel@gnu.org \
    --cc=development@efficientek.com \
    --cc=scdbackup@gmx.net \
    /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.