On 2025-04-13 Su 1:51 PM, Andres Freund wrote:
Hi,
On April 13, 2025 7:27:33 PM GMT+02:00, Wolfgang Walther
wrote:
Andrew Dunstan:
On 2025-04-12 Sa 10:10 PM, Noah Misch wrote:
On Sat, Apr 12, 2025 at 07:51:06PM +0200, Wolfgang Walther wrote:
With injection points enabled, I get the follo
Hi,
On April 13, 2025 7:27:33 PM GMT+02:00, Wolfgang Walther
wrote:
>Andrew Dunstan:
>>
>> On 2025-04-12 Sa 10:10 PM, Noah Misch wrote:
>>> On Sat, Apr 12, 2025 at 07:51:06PM +0200, Wolfgang Walther wrote:
With injection points enabled, I get the following errors in test_aio:
Andrew Dunstan:
On 2025-04-12 Sa 10:10 PM, Noah Misch wrote:
On Sat, Apr 12, 2025 at 07:51:06PM +0200, Wolfgang Walther wrote:
With injection points enabled, I get the following errors in test_aio:
[15:14:45.408](0.000s) not ok 187 - worker: first hard IO error is
reported:
expected stderr
On 2025-04-12 Sa 10:10 PM, Noah Misch wrote:
On Sat, Apr 12, 2025 at 07:51:06PM +0200, Wolfgang Walther wrote:
With injection points enabled, I get the following errors in test_aio:
[15:14:45.408](0.000s) not ok 187 - worker: first hard IO error is reported:
expected stderr
[15:14:45.409](0.0
On Sat, Apr 12, 2025 at 07:51:06PM +0200, Wolfgang Walther wrote:
> With injection points enabled, I get the following errors in test_aio:
>
>
> [15:14:45.408](0.000s) not ok 187 - worker: first hard IO error is reported:
> expected stderr
> [15:14:45.409](0.000s)
> [15:14:45.409](0.000s) # Fai
I recently enabled more features on my two buildfarm animals basilisk
and dogfish, which are running on Alpine with musl-libc in a docker
container.
--with-libnuma and --with-liburing seemed to work fine and have been
enabled for the last few runs, but --enable-injection-points does not [1].
