From: Leah Rumancik <leah.rumancik@gmail.com>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: fstests@vger.kernel.org
Subject: Re: [PATCH] check: wipe tmp.arglist
Date: Mon, 19 Dec 2022 11:03:51 -0800 [thread overview]
Message-ID: <Y6C1lyZuJMrjOVzA@google.com> (raw)
In-Reply-To: <Y5tG94XQmBziqveE@magnolia>
Oops, I originally ran into this when I was testing using /var/tmp
instead of /tmp [1], but since we aren't going this route anymore,
I don't need this for my use case. I am attempting to auto-recover when
a test crashes and relaunch the remaining tests and I was seeing some
tests being rerun due to the lingering tmp.arglist file.
This could occur on the off chance someone's /tmp is persistent or if
there wasn't a clean shutdown, maybe via an OOM kill? Perhaps it is
worth including for consistency's sake. I can update the commit
description if we want to keep it. Let me know your thoughts.
- Leah
[1] https://lore.kernel.org/fstests/20221212230646.4022294-1-leah.rumancik@gmail.com/
prev parent reply other threads:[~2022-12-19 19:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-14 21:59 [PATCH] check: wipe tmp.arglist Leah Rumancik
2022-12-15 11:36 ` David Disseldorp
2022-12-15 16:10 ` Darrick J. Wong
2022-12-19 19:03 ` Leah Rumancik [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=Y6C1lyZuJMrjOVzA@google.com \
--to=leah.rumancik@gmail.com \
--cc=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
/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