Git development
 help / color / mirror / Atom feed
From: Paul Tarjan <paul@paultarjan.com>
To: git@vger.kernel.org
Cc: peff@peff.net, szeder.dev@gmail.com, gitster@pobox.com,
	ps@pks.im, gitgitgadget@gmail.com
Subject: Re: [PATCH v14 12/13] fsmonitor: add tests for Linux
Date: Wed, 15 Apr 2026 07:26:15 -0600	[thread overview]
Message-ID: <20260415132615.47913-1-github@paulisageek.com> (raw)
In-Reply-To: <20260414221335.GA3413665@coredump.intra.peff.net>

Jeff King <peff@peff.net> writes:

> Do we need to put it in curly braces to avoid interfering with the &&
> chain? Otherwise a failure of anything before the maybe_timeout will hit
> the "||".

Good point. Fixed in v15:

  stop_daemon_delete_repo () {
      r=$1 &&
      { maybe_timeout 30 git -C $r fsmonitor--daemon stop 2>/dev/null || :; } &&
      rm -rf $1
  }

Thanks for catching this. The broken &&-chain and
2>/dev/null were hiding the test_might_fail error.

Verified that test_might_fail rejects maybe_timeout (exit code 1,
command never runs), while the { ... || :; } version actually
executes the stop. No other instances of test_might_fail maybe_timeout in the
repo.

Paul

       reply	other threads:[~2026-04-15 13:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20260414221335.GA3413665@coredump.intra.peff.net>
2026-04-15 13:26 ` Paul Tarjan [this message]
2026-04-06 17:54 [PATCH v13 00/13] fsmonitor: implement filesystem change listener for Linux Paul Tarjan via GitGitGadget
2026-04-09  4:59 ` [PATCH v14 " Paul Tarjan via GitGitGadget
2026-04-09  4:59   ` [PATCH v14 12/13] fsmonitor: add tests " Paul Tarjan via GitGitGadget
2026-04-14 20:20     ` SZEDER Gábor
2026-04-14 20:40       ` Junio C Hamano
2026-04-14 22:13         ` Jeff King

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=20260415132615.47913-1-github@paulisageek.com \
    --to=paul@paultarjan.com \
    --cc=git@vger.kernel.org \
    --cc=gitgitgadget@gmail.com \
    --cc=gitster@pobox.com \
    --cc=peff@peff.net \
    --cc=ps@pks.im \
    --cc=szeder.dev@gmail.com \
    /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