Ignore warnings from uring IO

[ellert]

Tests randomly fail because the uring memory is exhausted.

Here are some examples:

[ RUN      ] RNTuple.RandomAccess
.../root-6.36.00/core/testsupport/src/TestSupport.cxx:79: Failure
Failed
Received unexpected diagnostic of severity 2000 at 'RIoUring' reading 'io_uring is unexpectedly not available because:
Failed to allocate memory for the smallest possible io_uring instance. 'memlock' memory has been exhausted for this user'.
Suppress those using ROOT/TestSupport.hxx
.../root-6.36.00/core/testsupport/src/TestSupport.cxx:79: Failure
Failed
Received unexpected diagnostic of severity 2000 at 'RRawFileUnix' reading 'io_uring setup failed, falling back to blocking I/O in ReadV'.
Suppress those using ROOT/TestSupport.hxx
[  FAILED  ] RNTuple.RandomAccess (20472 ms)

[ RUN      ] RNTupleDSTest.ChainMT
.../root-6.34.08/core/testsupport/src/TestSupport.cxx:79: Failure
Failed
Received unexpected diagnostic of severity 2000 at 'RIoUring' reading 'io_uring is unexpectedly not available because:
Failed to allocate memory for the smallest possible io_uring instance. 'memlock' memory has been exhausted for this user'.
Suppress those using ROOT/TestSupport.hxx
.../root-6.34.08/core/testsupport/src/TestSupport.cxx:79: Failure
Failed
Received unexpected diagnostic of severity 2000 at 'RRawFileUnix' reading 'io_uring setup failed, falling back to blocking I/O in ReadV'.
Suppress those using ROOT/TestSupport.hxx
[  FAILED  ] RNTupleDSTest.ChainMT (1004 ms)

[github-actions[bot]]

Test Results

    21 files      21 suites   3d 12h 19m 23s ⏱️  3 223 tests  3 223 ✅ 0 💤 0 ❌ 65 960 runs  65 960 ✅ 0 💤 0 ❌

Results for commit bf4a5879.

:recycle: This comment has been updated with latest results.