git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Derrick Stolee <stolee@gmail.com>
To: Torsten =?unknown-8bit?Q?B=C3=B6gershausen?= <tboegi@web.de>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: [Question] Unicode weirdness breaking tests on ZFS?
Date: Wed, 17 Nov 2021 13:35:32 -0500	[thread overview]
Message-ID: <5d1b5ce6-d9ff-1b2a-2ff2-19813c957a24@gmail.com> (raw)
In-Reply-To: <8a3d0d0e-cc82-b696-00f4-b71e6452e1bd@gmail.com>

On 11/17/2021 1:29 PM, Derrick Stolee wrote:
> On 11/17/2021 12:39 PM, Torsten =?unknown-8bit?Q?B=C3=B6gershausen?= wrote:
>> On Wed, Nov 17, 2021 at 06:06:13PM +0100, Torsten B??gershausen wrote:
>>> On Wed, Nov 17, 2021 at 05:12:26PM +0100, Torsten B??gershausen wrote:
>>>> I'll can have a look - just installing in a virtual machine.
>>>
>>> So, the virtual machine is up-and-running.
>>>
>>> I got 2 messages:
>>>
>>> ok 9 - rename (silent unicode normalization) # TODO known breakage vanished
>>> ok 10 - merge (silent unicode normalization) # TODO known breakage vanished
>>>
>>> Do you get the same ?
> 
> Halfway, I see this:
> 
> ok 9 - rename (silent unicode normalization) # TODO known breakage vanished
> not ok 10 - merge (silent unicode normalization) # TODO known breakage

Making this even more confusing, my original output shows both of
the TODOs vanishing, but I can't make that happen only running this
test. However, with "prove -j8 t00*.sh" I can get them to both
vanish:

Test Summary Report
-------------------
t0050-filesystem.sh           (Wstat: 0 Tests: 11 Failed: 0)
  TODO passed:   9-10
t0021-conversion.sh           (Wstat: 256 Tests: 41 Failed: 1)
  Failed test:  31
  Non-zero exit status: 1
Files=53, Tests=2896, 15 wallclock secs ( 0.59 usr  0.07 sys + 26.96 cusr 13.95 csys = 41.57 CPU)
Result: FAIL


  reply	other threads:[~2021-11-17 18:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-17 15:17 [Question] Unicode weirdness breaking tests on ZFS? Derrick Stolee
2021-11-17 15:41 ` Ævar Arnfjörð Bjarmason
2021-11-17 16:12 ` Torsten Bögershausen
2021-11-17 17:06   ` Torsten =?unknown-8bit?Q?B=C3=B6gershausen?=
2021-11-17 17:39     ` Torsten =?unknown-8bit?Q?B=C3=B6gershausen?=
2021-11-17 18:29       ` Derrick Stolee
2021-11-17 18:35         ` Derrick Stolee [this message]
2021-11-19 15:44           ` Torsten Bögershausen
2021-11-19 17:03             ` Junio C Hamano
2021-11-19 18:30               ` Derrick Stolee

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=5d1b5ce6-d9ff-1b2a-2ff2-19813c957a24@gmail.com \
    --to=stolee@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=tboegi@web.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.
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 NNTP newsgroup(s).