Hi,
On Wed, 13 Aug 2025 at 23:03, Andres Freund <andres@anarazel.de> wrote:
>
> Hi,
>
> On 2025-08-13 10:24:07 -0400, Andres Freund wrote:
> > > 2- Using '/DEBUG:FULL' instead of '/DEBUG:FASTLINK' in the Windows CI
> > > task but this causes more memory to be used. It seems that the error
> > > appears only when the '/DEBUG:FASTLINK' is set. '/DEBUG:FULL' is a
> > > default option, so we may decide to not add it at all. I explicitly
> > > added it as I found this easier to understand. This approach fixes the
> > > build but I think it is not the correct fix, we will have one .pdb
> > > file after this fix; not one for each library type.
> >
> > I think it's an acceptable fix for now. I added /DEBUG:FASTLINK to the CI
> > task when it was using windows containers, as we'd run out of memory
> > occasionally. But since we aren't using those anymore, I think the best way to
> > make CI work again is to simply stop using /DEBUG:FASTLINK.
>
> I'll push it this way once the test completes that way in my repo. I want to
> get cfbot green again. If we want to do it differently than in Bilal's
> v2-0002-ci-windows-Use-DEBUG-FULL-instead-of-DEBUG-FASTLI.patch
Thank you!
> Separately I think we should report this as a bug to meson. Could you perhaps
> create a minimal reproducer of the issue and report it?
Yes, I will share the issue link for tracking when I report it.
--
Regards,
Nazir Bilal Yavuz
Microsoft
