Skip to content
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

SYCL-Unit :: scheduler/./SchedulerTests.exe/11/13 failing on Windows #15049

Open
sarnex opened this issue Aug 13, 2024 · 1 comment
Open

SYCL-Unit :: scheduler/./SchedulerTests.exe/11/13 failing on Windows #15049

sarnex opened this issue Aug 13, 2024 · 1 comment
Labels
bug Something isn't working confirmed

Comments

@sarnex
Copy link
Contributor

sarnex commented Aug 13, 2024

Describe the bug

FAIL: SYCL-Unit :: scheduler/./SchedulerTests.exe/11/13 (967 of 971)
******************** TEST 'SYCL-Unit :: scheduler/./SchedulerTests.exe/11/13' FAILED ********************
Script(shard):
--
GTEST_OUTPUT=json:D:\github\_work\llvm\llvm\build\tools\sycl\unittests\scheduler\.\SchedulerTests.exe-SYCL-Unit-5452-11-13.json GTEST_SHUFFLE=0 GTEST_TOTAL_SHARDS=13 GTEST_SHARD_INDEX=11 D:\github\_work\llvm\llvm\build\tools\sycl\unittests\scheduler\.\SchedulerTests.exe
--

Note: This is test shard 12 of 13.

[==========] Running 3 tests from 2 test suites.

[----------] Global test environment set-up.

[----------] 2 tests from SchedulerTest

[ RUN      ] SchedulerTest.StreamAUXCmdsWait

[       OK ] SchedulerTest.StreamAUXCmdsWait (1 ms)

[ RUN      ] SchedulerTest.StreamBufferDeallocation

Exception Code: 0xC0000005

#0 0x00007ff7a2759848 sycl::_V1::detail::Scheduler::NotifyHostTaskCompletion(class sycl::_V1::detail::Command *) D:\github\_work\llvm\llvm\src\sycl\source\detail\scheduler\scheduler.cpp:486:0

#1 0x00007ff7a274176e sycl::_V1::detail::DispatchHostTask::operator()(void) const D:\github\_work\llvm\llvm\src\sycl\source\detail\scheduler\commands.cpp:486:0

#2 0x00007ff7a26a69e6 sycl::_V1::detail::ThreadPool::worker(void) D:\github\_work\llvm\llvm\src\sycl\source\detail\thread_pool.hpp:51:0

#3 0x00007ff7a26a18e1 std::thread::_Invoke<class std::tuple<class `private: void __cdecl sycl::_V1::detail::ThreadPool::start(void)'::`3'::<lambda_1>>, 0>(void *) C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.33.31629\include\thread:56:0

#4 0x00007ffb4e106b4c (C:\WINDOWS\System32\ucrtbase.dll+0x26b4c)

#5 0x00007ffb4f1a4cb0 (C:\WINDOWS\System32\KERNEL32.DLL+0x14cb0)

#6 0x00007ffb5047e8ab (C:\WINDOWS\SYSTEM32\ntdll.dll+0x7e8ab)


--
exit: 3221225477
--
shard JSON output does not exist: D:\github\_work\llvm\llvm\build\tools\sycl\unittests\scheduler\.\SchedulerTests.exe-SYCL-Unit-5452-11-13.json
********************
Testing:  0.. 10.. 20.. 30.. 40.. 50.. 60.. 70.. 80.. 90.. 
********************
Failed Tests (1):
  SYCL-Unit :: scheduler/./SchedulerTests.exe/11/13

https://github.com/intel/llvm/actions/runs/10354169847/job/28658799648

https://github.com/intel/llvm/actions/runs/10362895613/job/28685641650

[ RUN      ] DependsOnTests.ShortcutFunctionWithWaitList

Exception Code: 0xC0000005

#0 0x00007ff71bacc1e0 sycl::_V1::detail::Scheduler::cleanupAuxiliaryResources(enum sycl::_V1::detail::BlockingT) D:\github\_work\llvm\llvm\src\sycl\source\detail\scheduler\scheduler.cpp:589:0

#1 0x00007ff71bacc439 sycl::_V1::detail::Scheduler::cleanupCommands(class std::vector<class sycl::_V1::detail::Command *, class std::allocator<class sycl::_V1::detail::Command *>> const &) D:\github\_work\llvm\llvm\src\sycl\source\detail\scheduler\scheduler.cpp:422:0

#2 0x00007ff71bac9b21 sycl::_V1::detail::Scheduler::NotifyHostTaskCompletion(class sycl::_V1::detail::Command *) D:\github\_work\llvm\llvm\src\sycl\source\detail\scheduler\scheduler.cpp:490:0

#3 0x00007ff71bab194e sycl::_V1::detail::DispatchHostTask::operator()(void) const D:\github\_work\llvm\llvm\src\sycl\source\detail\scheduler\commands.cpp:486:0

#4 0x00007ff71ba16b06 sycl::_V1::detail::ThreadPool::worker(void) D:\github\_work\llvm\llvm\src\sycl\source\detail\thread_pool.hpp:51:0

#5 0x00007ff71ba11a01 std::thread::_Invoke<class std::tuple<class `private: void __cdecl sycl::_V1::detail::ThreadPool::start(void)'::`3'::<lambda_1>>, 0>(void *) C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.33.31629\include\thread:56:0

#6 0x00007fffd0b76b4c (C:\WINDOWS\System32\ucrtbase.dll+0x26b4c)

#7 0x00007fffd28d4ed0 (C:\WINDOWS\System32\KERNEL32.DLL+0x14ed0)

#8 0x00007fffd321e40b (C:\WINDOWS\SYSTEM32\ntdll.dll+0x7e40b)


--
exit: 3221225477

https://github.com/intel/llvm/actions/runs/10374827332/job/28723151663?pr=14996

https://github.com/intel/llvm/actions/runs/10373080404/job/28717618786

To reproduce

No response

Environment

No response

Additional context

No response

@sarnex sarnex added bug Something isn't working confirmed labels Aug 13, 2024
sarnex added a commit that referenced this issue Aug 13, 2024
)

Failing on Windows

#15049

Signed-off-by: Sarnie, Nick <nick.sarnie@intel.com>
sarnex added a commit that referenced this issue Aug 13, 2024
…15060)

This one is failing too. Also tracked in
#15049

Signed-off-by: Sarnie, Nick <nick.sarnie@intel.com>
@sarnex
Copy link
Contributor Author

sarnex commented Aug 14, 2024

@intel/llvm-reviewers-runtime Someone should probably take a look at these. They just started failing recently, so my guess is some commit is causing the sporadic fails on Windows. Thanks.

againull pushed a commit that referenced this issue Sep 10, 2024
A month ago, we had a strange intermittent failure of one of the unit
tests: #15049 and in response to
that we disabled the test. It is unclear why that might have been
failing.

But that was when there were some other disrupting changes, and fallout
from that has since been fixed.


I have retested this on Windows for 100,000 iterations, and not a single
failure seen. Tested on the CI, ran successfully there too.

I'd like to reenable this test with this PR. If the CI system starts
failing on PR, we can just revert this PR in coming days.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working confirmed
Projects
None yet
Development

No branches or pull requests

1 participant