From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Peter Geoghegan <pg(at)bowt(dot)ie> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Christoph Berg <myon(at)debian(dot)org>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pgsql: Add basic TAP tests for psql's tab-completion logic. |
Date: | 2020-01-04 02:16:42 |
Message-ID: | 22669.1578104202@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
Peter Geoghegan <pg(at)bowt(dot)ie> writes:
> Not sure if the specifics matter, but FWIW "make check-world" ended
> with the following failure just now:
> # Failed test 'offer multiple table choices'
> # at t/010_tab_completion.pl line 105.
> # Actual output was "\r\n\e[01;35mmytab\e[0m\e[K123\e[0m\e[K
> \e[01;35mmytab\e[0m\e[K246\e[0m\e[K \r\npostgres=# select * from
> mytab\r\n\e[01;35mmytab\e[0m\e[K123\e[0m\e[K
> \e[01;35mmytab\e[0m\e[K246\e[0m\e[K \r\npostgres=# select * from
> mytab"
Huh. What readline or libedit version are you using, on what
platform? I'm curious also what is your prevailing setting
of TERM? (I've been wondering if the test doesn't need to
force that to something standard. The buildfarm hasn't shown
any signs of needing that, but manual invocations might be
a different story.)
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Geoghegan | 2020-01-04 02:37:25 | Re: pgsql: Add basic TAP tests for psql's tab-completion logic. |
Previous Message | Peter Geoghegan | 2020-01-04 01:32:10 | Re: pgsql: Add basic TAP tests for psql's tab-completion logic. |
From | Date | Subject | |
---|---|---|---|
Next Message | Vik Fearing | 2020-01-04 02:32:34 | Re: Greatest Common Divisor |
Previous Message | Ashutosh Sharma | 2020-01-04 02:02:11 | Re: Assigning ROW variable having NULL value to RECORD type variable doesn't give any structure to the RECORD variable. |