Re: Windows regress fails (latest HEAD) - Mailing list pgsql-hackers

From Ranier Vilela
Subject Re: Windows regress fails (latest HEAD)
Date
Msg-id CAEudQAqWxyNmb8mtJmR+ZAxT0YXHLoOP7gOVdP+dCHewmz-kDQ@mail.gmail.com
Whole thread Raw
In response to Re: Windows regress fails (latest HEAD)  (Ranier Vilela <ranier.vf@gmail.com>)
Responses Re: Windows regress fails (latest HEAD)
List pgsql-hackers
Em sex., 26 de jun. de 2020 às 08:21, Ranier Vilela <ranier.vf@gmail.com> escreveu:
Em qui., 11 de jun. de 2020 às 10:28, Ranier Vilela <ranier.vf@gmail.com> escreveu:
Em qui., 11 de jun. de 2020 às 10:01, Andrew Dunstan <andrew.dunstan@2ndquadrant.com> escreveu:

On 6/11/20 8:52 AM, Ranier Vilela wrote:
> Hi,
> Latest HEAD, fails with windows regress tests.
>
>  float8                       ... FAILED      517 ms
>  partition_prune              ... FAILED     3085 ms
>
>

The first thing you should do when you find this is to see if there is a
buildfarm report of the failure. If there isn't then try to work out why.
Sorry, I will have to research the buildfarm, I have no reference to it.
 

Also, when making a report like this, it is essential to let us know
things like:

  * which commit is causing the failure (git bisect is good for finding
    this)
Thanks for hit (git bisect).
 
  * what Windows version you're testing on
Windows 10 (2004)

  * which compiler you're using
msvc 2019 (64 bits)

Only for registry, if anyone else is using msvc 2019.
I'm using latest msvc 2019 64 bits (16.6.0)
Problably this is a compiler optimization bug.
vcregress check with build DEBUG, pass all 200 tests.
With the current HEAD, the regression float8 in release mode (msvc 2019 64 bits) is gone.
Maybe it's this commit:
https://github.com/postgres/postgres/commit/0aa8f764088ea0f36620ae2955fa6c54ec736c46

But (partition_prune) persists.
partition_prune              ... FAILED
 
regards,
Ranier Vilela

pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: Fix for parallel BTree initialization bug
Next
From: Daniel Gustafsson
Date:
Subject: Re: Proposal of new PostgreSQL Extension - PGSpiderExt