On Sat, Oct 12, 2019 at 3:56 PM Peter Eisentraut <peter.eisentr...@2ndquadrant.com> wrote: > > On 2019-10-03 16:21, Andrew Dunstan wrote: > > My new msys2 animal fairywren > > Could you please check how this animal is labeled? AFAICT, this is not > an msys2 build but a mingw build (x86_64-w64-mingw32).
It is indeed an msys2 system. However, when we set MSYSTEM=MINGW64 as we do in fairywren's config environment so that the compiler it is properly detected by configure (using Msys2's /etc/config.site) 'uname -a' reports MINGW64... instead of MSYS... This is a bit confusing. The compiler currently being used on the animal is the gcc 7.3.0 from the Mingw64 project, the same one that's being usied on jacana (which runs Msys1). Notwithstanding the "mingw32" in the compiler name, these are 64 bit builds. I think the "32" there is somewhat vestigial. > > > has had 3 recent failures when checking > > pg_upgrade. The failures have been while running the regression tests, > > specifically the interval test, and they all look like this: > > I've also seen this randomly, but only under 64-bit mingw, never 32-bit > mingw. > Since I downgraded the compiler from gcc 9.0 about a week ago these errors seem to have stopped. cheers andrew -- Andrew Dunstan https://www.2ndQuadrant.com PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
