Re: Increase pltcl test coverage

From: Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, Karl Lehenbauer <karl(at)flightaware(dot)com>
Subject: Re: Increase pltcl test coverage
Date: 2017-01-09 21:12:07
Message-ID: 1f13802c-df1e-c998-09dc-1161c494e8d9@BlueTreble.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 1/9/17 1:22 PM, Tom Lane wrote:
> I wrote:
>> Pushed with that and some other, mostly-cosmetic changes.
>
> Hmm, looks like the new test cases have turned up a pre-existing bug.
> Some of the buildfarm is showing crashes :-(. It looks like all the
> unhappy critters are running Tcl 8.4.something, which might be a
> coincidence but I bet not.
>
> I get the impression it's a stack clobber or memory clobber associated
> with reporting Tcl errors back to PG, but haven't been able to isolate
> it yet.

I notice the failures are also on "unusual" platforms, with only 1 being
x86. Though, that's very possibly the only animals running 8.4...

I'm compiling 8.4 now, will see if I can duplicate.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
855-TREBLE2 (855-873-2532)

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2017-01-09 21:14:57 Re: proposal: session server side variables
Previous Message Alvaro Herrera 2017-01-09 21:03:51 Re: Incorrect XLogRegisterBuffer flag for revmapbuf in brin