On Tue, Nov 10, 2020 at 04:22:37PM -0500, Russell Foster wrote: > Never claimed they were the same, but they are both Windows x64. Here > are some more details: > > Test Passes: > VM machine (Build Server) > Microsoft Windows 10 Pro > Version 10.0.18363 Build 18363 > Microsoft (R) C/C++ Optimizing Compiler Version 19.27.29112 for x64 > > Compile args: > C:\Program Files (x86)\Microsoft Visual > Studio\2019\Enterprise\VC\Tools\MSVC\14.27.29110\bin\HostX86\x64\CL.exe > /c /Isrc/include /Isrc/include/port/win32 > /Isrc/include/port/win32_msvc /Iexternals/zlib > /Iexternals/openssl\include /Isrc/backend /Zi /nologo /W3 /WX- > /diagnostics:column /Ox /D WIN32 /D _WINDOWS /D __WINDOWS__ /D > __WIN32__ /D EXEC_BACKEND /D WIN32_STACK_RLIMIT=4194304 /D > _CRT_SECURE_NO_DEPRECATE /D _CRT_NONSTDC_NO_DEPRECATE /D BUILDING_DLL > /D _MBCS /GF /Gm- /EHsc /MD /GS /fp:precise /Zc:wchar_t /Zc:forScope > /Zc:inline /Fo".\Release\postgres\\" /Fd".\Release\postgres\vc142.pdb" > /Gd /TC /wd4018 /wd4244 /wd4273 /wd4102 /wd4090 /wd4267 /FC > /errorReport:queue /MP src/backend/catalog/partition.c
drongo is the closest thing we have in the buildfarm for this setup. Here is the boring option part when it comes to Postgres compilation: https://buildfarm.postgresql.org/cgi-bin/show_stage_log.pl?nm=drongo&dt=2020-11-10%2018%3A59%3A20&stg=make C:\\Program Files (x86)\\Microsoft Visual Studio\\2019\\BuildTools\\VC\\Tools\\MSVC\\14.23.28105\\bin\\HostX86\\x64\\CL.exe /c /Isrc/include /Isrc/include/port/win32 /Isrc/include/port/win32_msvc /Ic:\\prog\\3p64\\include /I"C:\\Program Files\\OpenSSL-Win64\\include" /Isrc/backend /Zi /nologo /W3 /WX- /diagnostics:column /Ox /D WIN32 /D _WINDOWS /D __WINDOWS__ /D __WIN32__ /D WIN32_STACK_RLIMIT=4194304 /D _CRT_SECURE_NO_DEPRECATE /D _CRT_NONSTDC_NO_DEPRECATE /D BUILDING_DLL /D _MBCS /GF /Gm- /EHsc /MD /GS /fp:precise /Zc:wchar_t /Zc:forScope /Zc:inline /Fo".\\Release\\postgres\\\\" /Fd".\\Release\\postgres\\vc142.pdb" /Gd /TC /wd4018 /wd4244 /wd4273 /wd4102 /wd4090 /wd4267 /FC /errorReport:queue /MP [ source files ] [...] So except if I am missing something we have an exact match here. > Test Fails: > Laptop machine (Development) > Microsoft Windows 10 Enterprise > Version 10.0.19041 Build 19041 > Microsoft (R) C/C++ Optimizing Compiler Version 19.27.29112 for x64 > > Compile args: > C:\Program Files (x86)\Microsoft Visual > Studio\2019\Enterprise\VC\Tools\MSVC\14.27.29110\bin\HostX86\x64\CL.exe > /c /Isrc/include /Isrc/include/port/win32 > /Isrc/include/port/win32_msvc /Iexternals/zlib > /Iexternals/openssl\include /Isrc/backend /Zi /nologo /W3 /WX- > /diagnostics:column /Ox /D WIN32 /D _WINDOWS /D __WINDOWS__ /D > __WIN32__ /D EXEC_BACKEND /D WIN32_STACK_RLIMIT=4194304 /D > _CRT_SECURE_NO_DEPRECATE /D _CRT_NONSTDC_NO_DEPRECATE /D BUILDING_DLL > /D _MBCS /GF /Gm- /EHsc /MD /GS /fp:precise /Zc:wchar_t /Zc:forScope > /Zc:inline /Fo".\Release\postgres\\" /Fd".\Release\postgres\vc142.pdb" > /Gd /TC /wd4018 /wd4244 /wd4273 /wd4102 /wd4090 /wd4267 /FC > /errorReport:queue /MP src/backend/catalog/partition.c And this configuration matches exactly what you have with the host where the test passed. Now I do see a difference in the Windows 10 build involved, 10.0.19041 fails but 10.0.18363 passes. I find rather hard to buy that this is directly a Postgres bug. The compiler version is the same, so the issue seems to be related to the way the code compiled is interpreted. -- Michael
signature.asc
Description: PGP signature
