From: Andrei Rybak <rybak.a.v@gmail.com>
To: git@vger.kernel.org
Cc: Eric Sunshine <sunshine@sunshineco.com>,
Tim Schumacher <timschumi@gmx.de>,
Jeff Hostetler <jeffhost@microsoft.com>,
Robin Rosenberg <robin.rosenberg@dewire.com>
Subject: [PATCH v1 0/3] fixes for commented out code in tests (was "Re: [PATCH] *: fix typos which duplicate a word")
Date: Thu, 12 Jan 2023 00:32:39 +0100 [thread overview]
Message-ID: <20230111233242.16870-1-rybak.a.v@gmail.com> (raw)
In-Reply-To: CAPig+cTgUPWxMox_nSka52dML6_GHUUoY4HCtcq7+7J0oEyeNw@mail.gmail.com
[ I apologize for some people getting this twice -- I messed up when
invoking `git send-email` ]
On 2023-01-06T19:25, Eric Sunshine wrote:
> Not related to your patch at all, but I notice in this test that the
> call to test_when_finished() is commented out:
>
> # test_when_finished "stop_daemon_delete_repo test_insensitive" &&
>
> which makes me wonder if it was commented out while the test was being
> debugged but then forgotten, and that the script is now potentially
> leaking a running daemon if something in the test fails after the
> daemon was started, or if the daemon does not shut down on its own as
> it's supposed to do. [cc:+Jeff Hostetler]
Here's a patch series that fixes some of the commented out test code.
I skipped changing the following:
1. a minute-long test_expect_failure is commented out in t0014-alias.sh .
Technically, this could be uncommented and marked with `EXPENSIVE`
prerequisite, but it doesn't seem worth it for a `test_expect_failure`.
[ cc Tim Schumacher, who added this test in fef5f7fc43 (t0014: introduce an
alias testing suite, 2018-09-16) ]
2. In t6426-merge-skip-unneeded-updates.sh, second part of the test '2c: Modify
b & add c VS rename b->c' is commented out with an explicit "# FIXME:
rename/add conflicts are horribly broken right now;" above the commented out
part.
[ cc Elijah Newren, author of c04ba51739 (t6046: testcases checking whether
updates can be skipped in a merge, 2018-04-19) ]
3. I've experimented a bit with commented out test in file
t9200-git-cvsexportcommit.sh. Tests in this file rely on state from previous
tests, which complicates more thorough investigation. Unfortunately, I
didn't have bandwidth to investigate this further.
[ cc Robin Rosenberg, who added it in fe142b3a45 (Rework cvsexportcommit to
handle binary files for all cases., 2006-11-12) and commented out in
e86ad71fe5 (Make cvsexportcommit work with filenames with spaces and
non-ascii characters., 2006-12-11) ]
I found these places in tests with:
git grep -P '^\s*[#]\s*test_' -- 't/t[0-9]*'
The rest of the results of this grep are documentation comments.
Andrei Rybak (3):
t6003: uncomment test '--max-age=c3, --topo-order'
t6422: drop commented out code
t7527: uncomment test_when_finished step in a test
t/t6003-rev-list-topo-order.sh | 23 ++++++++++-------------
t/t6422-merge-rename-corner-cases.sh | 2 --
t/t7527-builtin-fsmonitor.sh | 2 +-
3 files changed, 11 insertions(+), 16 deletions(-)
--
2.39.0
next reply other threads:[~2023-01-11 23:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-11 23:32 Andrei Rybak [this message]
2023-01-11 23:32 ` [PATCH v1 1/3] t6003: uncomment test '--max-age=c3, --topo-order' Andrei Rybak
2023-01-11 23:32 ` [PATCH v1 2/3] t6422: drop commented out code Andrei Rybak
2023-01-11 23:32 ` [PATCH v1 3/3] t7527: use test_when_finished in 'case insensitive+preserving' Andrei Rybak
2023-01-14 9:43 ` Eric Sunshine
2023-01-12 0:45 ` [PATCH v1 0/3] fixes for commented out code in tests (was "Re: [PATCH] *: fix typos which duplicate a word") Tim Schumacher
2023-01-12 1:54 ` Elijah Newren
2023-01-13 4:32 ` Elijah Newren
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230111233242.16870-1-rybak.a.v@gmail.com \
--to=rybak.a.v@gmail.com \
--cc=git@vger.kernel.org \
--cc=jeffhost@microsoft.com \
--cc=robin.rosenberg@dewire.com \
--cc=sunshine@sunshineco.com \
--cc=timschumi@gmx.de \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).