Re: TEMP_CONFIG vs test_aio

Todd Cook <cookt@blackduck.com>

From: Todd Cook <cookt@blackduck.com>

To: Andres Freund <andres@anarazel.de>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>

Cc: Noah Misch <noah@leadboat.com>

Date: 2025-04-01T20:12:29Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

tests: Cope with io_method in TEMP_CONFIG in test_aio
- 327d987df1e7 18.0 landed
aio: Add test_aio module
- 93bc3d75d8e1 18.0 cited

On 4/1/25, 3:42 PM, "Andres Freund" <andres@anarazel.de <mailto:andres@anarazel.de>> wrote:
> I just committed the tests for AIO, and unfortunately they (so far) fail on
> one buildfarm animal:
> https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=bumblebee&dt=2025-04-01%2018%3A55%3A01 <https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=bumblebee&amp;dt=2025-04-01%2018%3A55%3A01>
>
> The reason for the failure is simple, the buildfarm animal specifies
> io_method=io_uring (thanks to "cookt" for setting that up so quickly, whoever
> you are :)) and the test is assuming that the -c io_method=... it passes to
> initdb is actually going to be used, but it's overwritten by the TEMP_CONFIG.

You're welcome!

Is there an alternate way I could use to configure the io_method on bumblebee?

-- todd