Re: [ANNOUNCE] Git v2.23.0-rc0 - Initial test failures on NonStop
- From
René Scharfe <l.s.r@web.de>
- Date
- Jul 31, 2019, 04:06 UTC
- Message-ID
- <b32a178d-0255-6c82-a3fd-ced2ec828fc8@web.de>
- In-Reply-To
- <20190731032735.GA14684@sigill.intra.peff.net>
Am 31.07.19 um 05:27 schrieb Jeff King:
Show 9 quoted lines
> One thing that makes it all a bit funky is that the "put" lines also > output the old value (which is what all those NULLs) are. And I think > that solves my "value3" puzzlement from earlier. It is not part of the > iteration at all, but rather the result of the duplicate "put". > > That would perhaps be clearer if the "hashmap" tool actually did the > sorting itself (so we'd sort _just_ the iteration, not the whole > output). Something like this, though I'm on the fence about whether it > is worth it:
We already have a few other tests that sort and compare. Perhaps it's time for a test_cmp_ignore_order?
And perhaps something like this might even be worth implementing as a diff option? https://github.com/l0b0/diff-ignore-moved-lines has post-processing script for that..
René