Hello Daniel and Zsolt, 05.11.2026 23:17, Daniel Gustafsson wrote:
I pushed this earlier today, but according the buildfarm the backpatch of the test to 18 wasn't entirely correct. Will fix when back at the laptop.
Recent changes to oauth_validator/001_server.pl increased its duration so it fails now on overloaded (due to concurrent activity?) animals, like in [1] and [2]: # die: IPC::Run: timeout on timer #1 at /usr/share/perl5/IPC/Run.pm line 3361. # Looks like your test exited with 29 just after 151. # die: IPC::Run: timeout on timer #1 at /usr/share/perl5/IPC/Run.pm line 3361. # Looks like your test exited with 2 just after 133. Logs of these animals show that other tests also ran for longer in these runs, e.g. compare [2]: 218/401 recovery - postgresql:recovery/027_stream_regress OK 1048.99s 11 subtests passed 392/401 oauth_validator - postgresql:oauth_validator/001_server ERROR 191.48s exit status 2 vs the next successful run [3] 183/401 recovery - postgresql:recovery/027_stream_regress OK 88.70s 11 subtests passed 400/401 oauth_validator - postgresql:oauth_validator/001_server OK 55.08s 173 subtests passed Out of 200+ animals, only 25 have "oauth" in PG_TEST_EXTRA plus libcurl enabled -- this can explain why definitely slower animals didn't fail the test. Could you please look if the test can be made more resilient against such slowdowns? [1] https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=grassquit&dt=2026-11-07%2000%3A31%3A47 [2] https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=olingo&dt=2026-11-07%2000%3A31%3A30 [3] https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=olingo&dt=2026-11-07%2002%3A52%3A57 Best regards, Alexander
