From: Junio C Hamano <gitster@pobox.com>
To: Patrick Steinhardt <ps@pks.im>
Cc: Johannes Schindelin via GitGitGadget <gitgitgadget@gmail.com>,
git@vger.kernel.org,
Johannes Schindelin <johannes.schindelin@gmx.de>
Subject: Re: [PATCH] ci(win+Meson): build in Release mode, avoiding t7001-mv hangs
Date: Mon, 28 Apr 2025 10:01:34 -0700 [thread overview]
Message-ID: <xmqq8qnkdxu9.fsf@gitster.g> (raw)
In-Reply-To: <aA8ymUzWM2t0QkFP@pks.im> (Patrick Steinhardt's message of "Mon, 28 Apr 2025 09:47:37 +0200")
Patrick Steinhardt <ps@pks.im> writes:
>> > The reason for this timeout is the test case 'nonsense mv triggers
>> > assertion failure and partially updated index' in t7001-mv (which is
>> > not even a regression test, but instead merely demonstrates a bug that
>> > someone thought someone else should fix at some time). As the name
>> > suggests, it triggers an assertion. The problem with this is that an
>> > assertion on Windows, at least when run in Debug mode, will open a modal
>> > dialog that patiently awaits some buttons to be clicked. Which never
>> > happens in automated builds.
>>
>> Interesting.
>>
>> So another viable fix (no, I am not suggesting a counter-proposal,
>> but asking a pure question to see if I understand the issue
>> correctly) is to rewrite "assert(cond)" to "if (cond) BUG(...)"
>> or something like that, so that it truly fails?
>
> On the surface this sounds like a reasonable thing to do, but I don't
> have enough context to be really able to tell.
Interesting again ;-) I didn't realize that it was a fairly recent
development. 0fcd473f (t7001: add failure test which triggers
assertion, 2024-10-22) is what adds the questionable test.
And I do agree with Dscho's assessment that this is "show a bug
without bothering to fix it", which is not what we usually take
without first exploring how involved the necessary fix would be.
I wonder in what bad status would a production build that simply
disabled the assert() is leaving the resulting repository.
Quoting from the last part of my response [*] to the initial report
that eventually turned into the test after 9 months:
[*] https://lore.kernel.org/git/xmqqil47obnw.fsf@gitster.g/
---- snip snap ----
Thanks for reporting, Kristoffer.
Any takers?
$ git shortlog --since=3.years -s -n -e --no-merges v2.43.0 builtin/mv.c
15 Shaoxuan Yuan <shaoxuan.yuan02@gmail.com>
10 Elijah Newren <newren@gmail.com>
5 Ævar Arnfjörð Bjarmason <avarab@gmail.com>
2 Junio C Hamano <gitster@pobox.com>
1 Andrzej Hunt <ajrhunt@google.com>
1 Calvin Wan <calvinwan@google.com>
1 Derrick Stolee <stolee@gmail.com>
1 Sebastian Thiel <sebastian.thiel@icloud.com>
1 Torsten Bögershausen <tboegi@web.de>
next prev parent reply other threads:[~2025-04-28 17:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-25 15:05 [PATCH] ci(win+Meson): build in Release mode, avoiding t7001-mv hangs Johannes Schindelin via GitGitGadget
2025-04-25 15:18 ` Junio C Hamano
2025-04-28 7:47 ` Patrick Steinhardt
2025-04-28 17:01 ` Junio C Hamano [this message]
2025-04-29 12:20 ` Patrick Steinhardt
2025-04-29 20:48 ` Junio C Hamano
2025-04-30 8:58 ` Patrick Steinhardt
2025-04-30 12:46 ` Patrick Steinhardt
2025-04-29 20:57 ` Kristoffer Haugsbakk
2025-05-03 14:25 ` [PATCH v2] ci(win+Meson): build in Release mode Johannes Schindelin via GitGitGadget
2025-05-05 6:06 ` Patrick Steinhardt
2025-05-05 7:27 ` Johannes Schindelin
2025-05-05 9:43 ` Patrick Steinhardt
2025-05-05 15:54 ` Junio C Hamano
2025-05-06 7:57 ` Patrick Steinhardt
2025-05-06 8:32 ` Johannes Schindelin
2025-05-08 18:19 ` Junio C Hamano
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=xmqq8qnkdxu9.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=johannes.schindelin@gmx.de \
--cc=ps@pks.im \
/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.