Change Details

We had this quiet rare flaky behaviour with this test, and the error message was this one: aio short write (16384) So, once improved this error message, the new error message was: aio short write: got 16384, expected: 131584 (max_buf_aio=256, iovcnt=257) Now,

We had this quiet rare flaky behaviour with this test, and the error message was this one: aio short write (16384) So, once improved this error message, the new error message was: aio short write: got 16384, expected: 131584 (max_buf_aio=256, iovcnt=257) To reproduce easly: ``` $ sudo sysctl vfs.aio.max_buf_aio=256 vfs.aio.max_buf_aio: 16 -> 256 $sudo kyua test sys/aio/aio_test:vectored_big_iovcnt ``` But remember: There is nothing in the standard aio tests that is modifing the default value.

We had this quiet rare flaky behaviour with this test, and the error message was this one: aio short write (16384) So, once improved this error message, the new error message was: aio short write: got 16384, expected: 131584 (max_buf_aio=256, iovcnt=257) To reproduce easly: Now, ``` $ sudo sysctl vfs.aio.max_buf_aio=256 vfs.aio.max_buf_aio: 16 -> 256 $sudo kyua test sys/aio/aio_test:vectored_big_iovcnt ``` But remember: There is nothing in the standard aio tests that is modifing the default value.