oneapi-src / oneapi-src/unified-memory-framework

Sporadic fail in Level Zero IPC tests

Open
#1,169 9 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug high priority
Dominant language
C
Stars
98
Forks
48
Avg merge
3d 20h
Merged PRs (30d)
6

Description

Sporadic fail in Level Zero IPC tests

umfLevelZeroProviderTestSuite/umfIpcTest.ConcurrentGetConcurrentPutHandles/0

Environment Information

  • UMF version (hash commit or a tag): latest
  • OS(es) version(s): Ubuntu Release

Please provide a reproduction of the bug:

https://github.com/oneapi-src/unified-memory-framework/actions/runs/13719665034/job/38374211866?pr=1147

35/55 Test #35: test_provider_level_zero ......................***Exception: SegFault  0.17 sec
Running main() from /home/test-user/actions-runner/_work/unified-memory-framework/unified-memory-framework/build/_deps/googletest-src/googletest/src/gtest_main.cc
[==========] Running 46 tests from 4 test suites.
[----------] Global test environment set-up.

...

[----------] 14 tests from umfLevelZeroProviderTestSuite/umfIpcTest
[ RUN      ] umfLevelZeroProviderTestSuite/umfIpcTest.GetIPCHandleSize/0
[       OK ] umfLevelZeroProviderTestSuite/umfIpcTest.GetIPCHandleSize/0 (0 ms)
[ RUN      ] umfLevelZeroProviderTestSuite/umfIpcTest.GetIPCHandleSizeInvalidArgs/0
[       OK ] umfLevelZeroProviderTestSuite/umfIpcTest.GetIPCHandleSizeInvalidArgs/0 (0 ms)
[ RUN      ] umfLevelZeroProviderTestSuite/umfIpcTest.GetIPCHandleInvalidArgs/0
[       OK ] umfLevelZeroProviderTestSuite/umfIpcTest.GetIPCHandleInvalidArgs/0 (0 ms)
[ RUN      ] umfLevelZeroProviderTestSuite/umfIpcTest.CloseIPCHandleInvalidPtr/0
[       OK ] umfLevelZeroProviderTestSuite/umfIpcTest.CloseIPCHandleInvalidPtr/0 (0 ms)
[ RUN      ] umfLevelZeroProviderTestSuite/umfIpcTest.BasicFlow/0
[       OK ] umfLevelZeroProviderTestSuite/umfIpcTest.BasicFlow/0 (4 ms)
[ RUN      ] umfLevelZeroProviderTestSuite/umfIpcTest.GetPoolByOpenedHandle/0
[       OK ] umfLevelZeroProviderTestSuite/umfIpcTest.GetPoolByOpenedHandle/0 (12 ms)
[ RUN      ] umfLevelZeroProviderTestSuite/umfIpcTest.AllocFreeAllocTest/0
[       OK ] umfLevelZeroProviderTestSuite/umfIpcTest.AllocFreeAllocTest/0 (1 ms)
[ RUN      ] umfLevelZeroProviderTestSuite/umfIpcTest.openInTwoIpcHandlers/0
[       OK ] umfLevelZeroProviderTestSuite/umfIpcTest.openInTwoIpcHandlers/0 (1 ms)
[ RUN      ] umfLevelZeroProviderTestSuite/umfIpcTest.ConcurrentGetConcurrentPutHandles/0

CRASH

How often bug is revealed:

rare

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Begin with the linked GitHub Actions run and the umfLevelZeroProviderTestSuite/umfIpcTest.ConcurrentGetConcurrentPutHandles/0 test, then run the Level Zero IPC test suite to determine whether the crash reproduces. Done means identifying and fixing the sporadic segfault and confirming that this test and the full provider test pass reliably.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
distributed-systems, testing-qa
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.