Hi, On 2025-04-01 20:12:29 +0000, Todd Cook wrote: > On 4/1/25, 3:42 PM, "Andres Freund" <and...@anarazel.de > <mailto:and...@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&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?
You could use PG_TEST_INITDB_EXTRA_OPTS, but I think you did it the right way. For one using PG_TEST_INITDB_EXTRA_OPTS would probably require changing the buildfarm code, because the buildfarm code filters out environment variables that aren't on an allowlist (I really dislike that). IOW, I think we should figure out a way to deal with TEMP_CONFIG containing io_method=io_uring, I just don't really know how yet. Greetings, Andres
