Skip to content

Ignore warnings from uring IO #18994

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

ellert
Copy link
Contributor

@ellert ellert commented Jun 7, 2025

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)

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)
Copy link

github-actions bot commented Jun 9, 2025

Test Results

    19 files      19 suites   3d 13h 8m 55s ⏱️
 2 805 tests  2 800 ✅ 0 💤 5 ❌
51 747 runs  51 742 ✅ 0 💤 5 ❌

For more details on these failures, see this check.

Results for commit 1c0b441.

@silverweed silverweed requested a review from hahnjo June 10, 2025 06:36
Copy link
Member

@hahnjo hahnjo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In general looks sensible, a suggestion inline

@@ -76,6 +76,20 @@ static struct ForbidDiagnostics {
return;
}

if (level == kWarning
&& strcmp(location, "RIoUring") == 0
&& strcmp(msg, "io_uring is unexpectedly not available because:\nFailed to allocate memory for the smallest possible io_uring instance. 'memlock' memory has been exhausted for this user") == 0) {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't know if we only want to check a substring of the message. This would make the code shorter and also makes future mistakes less likely where we change a part of the message.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants