Обсуждение: Increase OpenBSD CI task's RAM disk size

Hi,

Sometimes OpenBSD CI tasks fail with 'No space left on device' [1].
It's due to the OpenBSD CI task's RAM disk size being ~3.8 GB. This
patch increases it to ~4.6 GB. I chose this size manually, we can
increase it more.

Any feedback would be appreciated.

[1] https://cirrus-ci.com/task/4600833263796224

-- 
Regards,
Nazir Bilal Yavuz
Microsoft

> On 15 Aug 2025, at 10:46, Nazir Bilal Yavuz <byavuz81@gmail.com> wrote:

> Sometimes OpenBSD CI tasks fail with 'No space left on device' [1].
> It's due to the OpenBSD CI task's RAM disk size being ~3.8 GB. This
> patch increases it to ~4.6 GB. I chose this size manually, we can
> increase it more.

I don't know Cirrus enough to know if this is a daft question, but does this
impact the cost (in actual money or credits) for running the CI tests?

--
Daniel Gustafsson

Hi,

Thank you for looking into this!

On Fri, 15 Aug 2025 at 12:19, Daniel Gustafsson <daniel@yesql.se> wrote:
>
> > On 15 Aug 2025, at 10:46, Nazir Bilal Yavuz <byavuz81@gmail.com> wrote:
>
> > Sometimes OpenBSD CI tasks fail with 'No space left on device' [1].
> > It's due to the OpenBSD CI task's RAM disk size being ~3.8 GB. This
> > patch increases it to ~4.6 GB. I chose this size manually, we can
> > increase it more.
>
> I don't know Cirrus enough to know if this is a daft question, but does this
> impact the cost (in actual money or credits) for running the CI tests?

I don't expect this to increase costs, and it might even reduce them
slightly. Disks generally perform slower when free space is low, so
the change could make OpenBSD CI tasks faster.

-- 
Regards,
Nazir Bilal Yavuz
Microsoft

> On 15 Aug 2025, at 12:20, Nazir Bilal Yavuz <byavuz81@gmail.com> wrote:
> On Fri, 15 Aug 2025 at 12:19, Daniel Gustafsson <daniel@yesql.se> wrote:
>>
>>> On 15 Aug 2025, at 10:46, Nazir Bilal Yavuz <byavuz81@gmail.com> wrote:

>>> Sometimes OpenBSD CI tasks fail with 'No space left on device' [1].
>>> It's due to the OpenBSD CI task's RAM disk size being ~3.8 GB. This
>>> patch increases it to ~4.6 GB. I chose this size manually, we can
>>> increase it more.
>>
>> I don't know Cirrus enough to know if this is a daft question, but does this
>> impact the cost (in actual money or credits) for running the CI tests?
>
> I don't expect this to increase costs, and it might even reduce them
> slightly. Disks generally perform slower when free space is low, so
> the change could make OpenBSD CI tasks faster.

Thanks for clarifying, this definitely seems like something we should do to
keep tests from failing.

--
Daniel Gustafsson

Hi,

On 2025-09-02 10:24:34 +0200, Daniel Gustafsson wrote:
> > On 15 Aug 2025, at 12:20, Nazir Bilal Yavuz <byavuz81@gmail.com> wrote:
> > On Fri, 15 Aug 2025 at 12:19, Daniel Gustafsson <daniel@yesql.se> wrote:
> >> 
> >>> On 15 Aug 2025, at 10:46, Nazir Bilal Yavuz <byavuz81@gmail.com> wrote:
> 
> >>> Sometimes OpenBSD CI tasks fail with 'No space left on device' [1].
> >>> It's due to the OpenBSD CI task's RAM disk size being ~3.8 GB. This
> >>> patch increases it to ~4.6 GB. I chose this size manually, we can
> >>> increase it more.
> >> 
> >> I don't know Cirrus enough to know if this is a daft question, but does this
> >> impact the cost (in actual money or credits) for running the CI tests?
> > 
> > I don't expect this to increase costs, and it might even reduce them
> > slightly. Disks generally perform slower when free space is low, so
> > the change could make OpenBSD CI tasks faster.
> 
> Thanks for clarifying, this definitely seems like something we should do to
> keep tests from failing.

Pushed it now.

I've just enabled openbsd, netbsd and mingw to run by default on
postgres/postgres. If that works without a problem, I'll also enable it on
postgresql-cfbot.

Greetings,

Andres Freund