possible threading issue in the `io_uring_context`
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- cpp
- Domain
- operating-systems
Research direction
Start with test/exec/test_io_uring_context.cpp around lines 314 and 337, then run the io_uring_context schedule_after -1s test repeatedly as described. Trace the io_uring_context scheduling path to identify the intermittent failure, and consider the issue complete when the test passes reliably across repeated runs.
Written by the indexing model from the issue text.
Description
@lucteo reports in #1360 that he encountered the following test failure after running the stdexec tests 1000 times.
654: Test command: /github/workspace/build/gcc11-release/test/test.stdexec "io_uring_context schedule_after -1s"
654: Working Directory: /github/workspace/build/gcc11-release/test
654: Test timeout computed to be: 60
654: Filters: io_uring_context schedule_after -1s
654:
654: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
654: test.stdexec is a Catch v2.13.6 host application.
654: Run with -? for options
654:
654: -------------------------------------------------------------------------------
654: io_uring_context schedule_after -1s
654: -------------------------------------------------------------------------------
654: /github/workspace/test/exec/test_io_uring_context.cpp:314
654: ...............................................................................
654:
654: /github/workspace/test/exec/test_io_uring_context.cpp:337: FAILED:
654: CHECK( is_called_1 == true )
654: with expansion:
654: false == true
654:
654: ===============================================================================
654: test cases: 1 | 1 failed
654: assertions: 3 | 2 passed | 1 failed
654:
654/704 Test #654: io_uring_context schedule_after -1s ...........................................................................................***Failed 0.00 sec
Filters: io_uring_context schedule_after -1s
- Dominant language
- C++
- Stars
- 2.4k
- Forks
- 270
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 43
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from NVIDIA/stdexec
-
inline_scheduler's namespace-scope static_assert fails under nvcc (private nested __sender access) Open
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
-
Difficulty 4/5 3-5 days Newbie friendliness 65/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
duckdb/duckdb-wasm#2258 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
objectionary/eo-graphs#75 ·
-
Coarray integration tests carry no LABELS, so run_tests.py silently skips them under every backend Opencoarray
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
FISCO-BCOS/FISCO-BCOS#5642 ·