On Wed, 5 Feb 2025 at 21:05, Daniel Gustafsson wrote:
> For reference, you meant 53 right?
Yes, I meant 53
> If the
> CFBot always need one in "Future" state we should document that to make sure
> we
> don't miss that going forward (and perhaps automate it to make sure we dont
> make manual wor
> On 5 Feb 2025, at 20:36, Jelte Fennema-Nio wrote:
>
> On Wed, 5 Feb 2025 at 20:29, Jelte Fennema-Nio wrote:
>> I'll look into fixing that soonish. I took a quick look and it seems
>> related to some unexpected response from the Cirrus API.
>
> Okay I think I got it running again. It didn't li
On Wed, 5 Feb 2025 at 20:29, Jelte Fennema-Nio wrote:
> I'll look into fixing that soonish. I took a quick look and it seems
> related to some unexpected response from the Cirrus API.
Okay I think I got it running again. It didn't like that there was no
commitfest with number 54 yet. So I created
Hi,
On 2025-02-05 14:20:59 -0500, Tom Lane wrote:
> Andres Freund writes:
> > On 2025-02-05 14:09:02 -0500, Tom Lane wrote:
> >> Hard to tell, considering the cfbot has been completely wedged
> >> since Sunday.
>
> > It passed on the postgres repo just before this commit:
> > https://cirrus-ci
On Wed, 5 Feb 2025 at 20:21, Tom Lane wrote:
>
> Andres Freund writes:
> > On 2025-02-05 14:09:02 -0500, Tom Lane wrote:
> >> Hard to tell, considering the cfbot has been completely wedged
> >> since Sunday.
>
> > It passed on the postgres repo just before this commit:
> > https://cirrus-ci.com
Andres Freund writes:
> On 2025-02-05 14:09:02 -0500, Tom Lane wrote:
>> Hard to tell, considering the cfbot has been completely wedged
>> since Sunday.
> It passed on the postgres repo just before this commit:
> https://cirrus-ci.com/build/4733656549294080
> and then failed with it:
> https:
Hi,
On 2025-02-05 14:09:02 -0500, Tom Lane wrote:
> Jelte Fennema-Nio writes:
> > I guess you probably noticed, but in case you didn't: CI on windows is
> > still broken.
>
> Hard to tell, considering the cfbot has been completely wedged
> since Sunday.
It passed on the postgres repo just befor
Jelte Fennema-Nio writes:
> I guess you probably noticed, but in case you didn't: CI on windows is
> still broken.
Hard to tell, considering the cfbot has been completely wedged
since Sunday.
regards, tom lane
Hi,
On 2025-02-05 19:42:05 +0100, Jelte Fennema-Nio wrote:
> On Wed, 5 Feb 2025 at 00:22, Andres Freund wrote:
> > Pushed like that.
> >
> > I'll watch CI and BF over the next hours.
>
> I guess you probably noticed, but in case you didn't: CI on windows is
> still broken.
Huh. CI did pass on a
On Wed, 5 Feb 2025 at 00:22, Andres Freund wrote:
> Pushed like that.
>
> I'll watch CI and BF over the next hours.
I guess you probably noticed, but in case you didn't: CI on windows is
still broken.
Hi,
On 2025-02-04 12:46:42 -0500, Andres Freund wrote:
> On 2025-01-30 16:18:54 +0300, Nazir Bilal Yavuz wrote:
> > On Wed, 29 Jan 2025 at 19:50, Andres Freund wrote:
> > > I don't think that's the entirety of the issue.
> > >
> > > Our dependencies aren't quite airtight enough. With a sufficient
Hi,
On 2025-01-30 16:18:54 +0300, Nazir Bilal Yavuz wrote:
> On Wed, 29 Jan 2025 at 19:50, Andres Freund wrote:
> > I don't think that's the entirety of the issue.
> >
> > Our dependencies aren't quite airtight enough. With a sufficiently modern
> > meson, try doing e.g.
> >
> > rm -rf tmp_inst
Hi,
On Wed, 29 Jan 2025 at 19:50, Andres Freund wrote:
>
> On 2025-01-29 18:24:45 +0300, Nazir Bilal Yavuz wrote:
>
> > The cause is that meson fixed a bug [1] in v.1.7.0. Before meson
> > v1.7.0; although --no-rebuild is used while running tests, meson was
> > building all targets. This is fixed
Hi,
On 2025-01-29 18:24:45 +0300, Nazir Bilal Yavuz wrote:
> On Tue, 28 Jan 2025 at 17:02, Andres Freund wrote:
> >
> > Hi,
> >
> > On January 28, 2025 7:13:16 AM EST, Jelte Fennema-Nio
> > wrote:
> > >Since about ~11 hours ago the ecpg test is consistently failing on
> > >Window with this erro
Hi,
On Tue, 28 Jan 2025 at 17:02, Andres Freund wrote:
>
> Hi,
>
> On January 28, 2025 7:13:16 AM EST, Jelte Fennema-Nio
> wrote:
> >Since about ~11 hours ago the ecpg test is consistently failing on
> >Window with this error[1]:
> >
> >> Could not open file
> >> C:/cirrus/build/src/interfaces
Hi,
On January 28, 2025 7:13:16 AM EST, Jelte Fennema-Nio
wrote:
>Since about ~11 hours ago the ecpg test is consistently failing on
>Window with this error[1]:
>
>> Could not open file
>> C:/cirrus/build/src/interfaces/ecpg/test/compat_informix/dec_test.c for
>> reading
>
>I took a quick loo
Since about ~11 hours ago the ecpg test is consistently failing on
Window with this error[1]:
> Could not open file
> C:/cirrus/build/src/interfaces/ecpg/test/compat_informix/dec_test.c for
> reading
I took a quick look at possible causes but couldn't find a clear
winner. My current guess is th
17 matches
Mail list logo
