Re: BUG #16699: PostgreSQL failed to run "timetz" test on release and debug configuration with MSVC on windows
От | Magnus Hagander |
---|---|
Тема | Re: BUG #16699: PostgreSQL failed to run "timetz" test on release and debug configuration with MSVC on windows |
Дата | |
Msg-id | CABUevEzLd3qLJaCibc2NoMmrvD2AEeMMLiUm1SdwyFR2r+q=Ww@mail.gmail.com обсуждение исходный текст |
Ответ на | BUG #16699: PostgreSQL failed to run "timetz" test on release and debug configuration with MSVC on windows (PG Bug reporting form <noreply@postgresql.org>) |
Список | pgsql-bugs |
On Tue, Nov 3, 2020 at 11:29 AM PG Bug reporting form <noreply@postgresql.org> wrote: > > The following bug has been logged on the website: > > Bug reference: 16699 > Logged by: Gao Lin > Email address: gaolin01@beyondsoft.com > PostgreSQL version: 13.0 > Operating system: Windows Server 2016 > Description: > > Environment: > Windows Server 2016 + VS2019 + PostgreSQL master branch on babef40 commit. > > PostgreSQL failed to run "vcregress check parallel" due to one test "timetz" > on release and debug configuration with MSVC on windows. It can be produced > on master branch on babef40 commit. Could you please help look at this issue > ? Thanks a lot! This is most likely the timetz issues that showed up with the US DST changes, which have already been fixed in commit 4a071afbd056282746a5bc9362e87f579a56402d (along with backpatches). So if you move to the latest version of your branch, it should go away. That's a pretty stand-alone fix so you should be able to easily backpatch it to earlier versions if needed. > And I have one question: How to disable a single test "timetz" in "vcregress > check parallel" command line? The tests included in the parallel check are defined in src/test/regress/parallel_schedule. You should be able to remove it from there. -- Magnus Hagander Me: https://www.hagander.net/ Work: https://www.redpill-linpro.com/
В списке pgsql-bugs по дате отправления: