Hi,
On Thu, 11 Sept 2025 at 17:55, Jacob Champion
wrote:
>
> On Thu, Sep 11, 2025 at 7:18 AM Peter Eisentraut wrote:
> > I don't think we need this level of complication. We already have the
> > situation that for example "linux" covers several tasks
>
> Recently, I've wished that it were other
On 08.09.25 10:25, Nazir Bilal Yavuz wrote:
Tasks have short names to select them and the 'Windows VS 2019' task's
name was 'windows' (i.e: ci-os-only: windows) but since we have two
Windows tasks now; we need to have different names for VS 2019 and VS
2022 tasks. To preserve the same behavior,
Hi,
On Mon, 8 Sept 2025 at 11:25, Nazir Bilal Yavuz wrote:
>
> Example CI task after the PR is merged and 0002 is committed:
> https://cirrus-ci.com/build/5976334188412928 (I manually triggered the
> VS 2019 task, it will not be run automatically after the 0002 is
> committed).
I forgot to updat
Hi,
On 2025-09-15 11:50:07 +0300, Nazir Bilal Yavuz wrote:
> On Thu, 11 Sept 2025 at 17:55, Jacob Champion
> wrote:
> >
> > On Thu, Sep 11, 2025 at 7:18 AM Peter Eisentraut
> > wrote:
> > > I don't think we need this level of complication. We already have the
> > > situation that for example "
On Thu, Sep 11, 2025 at 7:18 AM Peter Eisentraut wrote:
> I don't think we need this level of complication. We already have the
> situation that for example "linux" covers several tasks
Recently, I've wished that it were otherwise; if I'm debugging a
Meson-only test failure in Linux, I don't wan
Hi,
On Fri, 6 Jun 2025 at 08:30, Peter Eisentraut wrote:
>
> On 05.06.25 12:42, Thomas Munro wrote:
> > I think on your C11 thread I might have been confused about that,
> > since there was an implication that 2019 might support ,
> > but it looks like 2019 added language stuff while 2022 added t
Hi,
On Fri, 6 Jun 2025 at 08:30, Peter Eisentraut wrote:
>
> On 05.06.25 12:42, Thomas Munro wrote:
> > I think on your C11 thread I might have been confused about that,
> > since there was an implication that 2019 might support ,
> > but it looks like 2019 added language stuff while 2022 added t
On 05.06.25 12:42, Thomas Munro wrote:
I think on your C11 thread I might have been confused about that,
since there was an implication that 2019 might support ,
but it looks like 2019 added language stuff while 2022 added the
library stuff. But yeah, given your proposal that MSVC 2019 should be
On Thu, Jun 5, 2025 at 8:48 PM Nazir Bilal Yavuz wrote:
> > Hmm, for the purposes of [0], I think it might be better to keep the
> > image at VS 2019 for now. Unless there are specific reasons why VS 2022
> > would be of use now?
>
> Thomas was thinking of trying some new APIs which are available
Hi,
On Thu, 5 Jun 2025 at 11:27, Peter Eisentraut wrote:
>
> On 05.06.25 10:04, Nazir Bilal Yavuz wrote:
> > Thomas Munro off-list mentioned that the Windows CI image is actually
> > running on Server 2022, even though the task name still refers to
> > Server 2019. He also suggested upgrading the
On 05.06.25 10:04, Nazir Bilal Yavuz wrote:
Thomas Munro off-list mentioned that the Windows CI image is actually
running on Server 2022, even though the task name still refers to
Server 2019. He also suggested upgrading the compiler from Visual
Studio 2019 to Visual Studio 2022.
Some of the ta
Hi,
Thomas Munro off-list mentioned that the Windows CI image is actually
running on Server 2022, even though the task name still refers to
Server 2019. He also suggested upgrading the compiler from Visual
Studio 2019 to Visual Studio 2022.
A PR [1] to upgrade the compiler to VS 2022 is ready in
12 matches
Mail list logo
