Thread: longfin

So, buildfarm member longfin is failing with:

test python3/hstore_plpython  ... FAILED (test process exited with exit code 2)

It claims that it's been failing since

6f3bd98 Tue Oct 4 15:01:42 2016 UTC  Extend framework from commit
53be0b1ad to report latch waits.

which would tend to pointer the finger at my commit that broke
everything else today.  However, I'm suspicious that this is actually
the fault of d51924be886c2a05e691fa05b16cb6b30ab8370f and/or
490ed1ebb9b26fb342a1e3240107092e9c5aec02 because I don't see how
changes to the latch stuff would break plpython.

However, I obviously missed a few things in 6f3bd98, so feel free to
tell me this is another case of me being dumb.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

Robert Haas <robertmhaas@gmail.com> writes:
> So, buildfarm member longfin is failing with:
> test python3/hstore_plpython  ... FAILED (test process exited with exit code 2)

Yeah, this is a side effect of what I'm working on, don't sweat it.

(The only reason it's passed at all today is that I put a copy of
libpython.dylib into where the existing configure script is expecting
to find it.  But I undid that after verifying that the build passed
with it.  I'm about to commit a proper fix.)
        regards, tom lane