Nazir Bilal Yavuz <byavuz81@gmail.com> writes:
> On Mon, 7 Jul 2025 at 13:51, Peter Eisentraut <peter@eisentraut.org> wrote:
>> Hmm. We have the (allegedly) same VS version in Cirrus CI, and it's
>> never shown a problem like this.
> CI uses the latest VS 2019 (v16.11.48), it looks like buildfarm member
> drongo uses VS 2019 v16.3.1. I created a custom Windows VM with the
> same VS 2019 version (v16.3.1) at the drongo and CI failed with the
> same error [1].
Huh. Can we trawl the release notes for VS and see if this was
acknowledged as a bug fix, and if so when did it happen? I think
whether we can say "get a newer compiler" depends in part on how
long it's been fixed.
regards, tom lane
