Re: Git-master regression failure

From: Svenne Krap <svenne(dot)lists(at)krap(dot)dk>
To: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Git-master regression failure
Date: 2013-06-18 19:41:28
Message-ID: 51C0B7E8.4070108@krap.dk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 18-06-2013 21:14, Jeff Janes wrote:
>
> But 9.2.4 does pass "make check", and only fails if you reproduce
those things manually?
>
No, I was lazy and used the (distribution-installed) 9.2....

I have tried "make check" on REL_9_2_4 and that fails to (same sole
failure)...

> If so, I'm guessing that you have some language/locale settings that "make check" neutralizes in
9.2.4, but that neutralization is broken in HEAD.
>
Nope, just never ran "make check" on it...
>
>
> As I have no real idea of what "~<~" is for an operator (I have looked
> it up as scalarltjoinsel), but I cannot find any semantics for it
in the
> docs*... So I have no way of manually checking the expected result.
>
>
>
> Yes, it does seem to be entirely undocumented. Using:
> git grep '~<~', I found the code comment "character-by-character (not
collation order) comparison operators for character types"
>
> Anyway, if REL9_2_4 passes make check, but 073d7cb513f5de44530f fails,
then you could use "git bisect" to find the exact commit that broke things.
>
It does not..

I will dig futher and get back...

Svenne
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.20 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQI5BAEBCAAjBQJRwLfnHBpodHRwOi8vc3Zlbm5lLmRrL3BncC9wb2xpY3kACgkQ
/zLSj+olL/J4oA/7Blq1eQarny6VVu7UUgtN+CWvy3zoiE36AlE/vEvzb4aXWP4c
5Mq8z3vkHrjKCdaioGYLrkEE2PTom+pBV5cK+cT67TAN1J/OJErtRuKhVLk2Bd8I
ry/gDgF8dvM0Sx03eN52ViCOjFUmksk+HXOSk8z0aPBdanbOdIQoSC25XJ2Yye8K
DP+yY6h9+PxMomMzaz3aK0MechZaJyvbLpStjJEd/nuAiDIymzpzxJfyjpn/jKra
6GVdRfQCMkqiBy5E4YFgxDkGfDJLFtwMJPMw8OAe+Zhgp8YLPSms58bwtdmwcPYD
NSfowZa/yaKpLP3k6J/2JVToa+JBPY/vYGlxdU+h15VmsDV8kxCWnRwxC/gYYg9l
7CqWPZskd9ZAonfb781JxoiVmoGbGzFCLE1wlPVazCZsAzQcvVTJD8yl/Ibv8PKv
7LjxuItm3iW8GAp93x7+MGmxKx/YKVu8lfAFTw2/X/G2MfoiJHmAUaklqdATerXl
xarQOL0UbiRGQNYSBHjKVxZHQrgAShPS2O2cSw6MijaDsr4US+pcY+S0F0KmtnD/
mobI3vSFFsZxnaIUAL4ExQuyF0PgGm7Ce4jmQxsUx7Ph/ud6AZVLhKStYBcwChPH
W+4Laq2fNB6/deH81x+x+j0QSk1oyvSVG+73/bmURWSP9WuhikYJ5kqbOdk=
=siUv
-----END PGP SIGNATURE-----

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Svenne Krap 2013-06-18 19:51:21 Re: Git-master regression failure
Previous Message Kevin Grittner 2013-06-18 19:34:38 Re: Git-master regression failure