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

Tests for DNNL_CPU_RUNTIME=THREADPOOL _DNNL_TEST_THREADPOOL_IMPL=STANDALONE freeze #877

Closed
yurivict opened this issue Nov 7, 2020 · 2 comments
Labels
sighting Suspicious library behavior. Should be promoted to a bug when confirmed

Comments

@yurivict
Copy link
Contributor

yurivict commented Nov 7, 2020

When oneDNN is built with DNNL_CPU_RUNTIME=THREADPOOL _DNNL_TEST_THREADPOOL_IMPL=STANDALONE tests freeze:

Test project /usr/ports/math/onednn/work/.build
      Start  1: api-c
 1/71 Test  #1: api-c .............................................   Passed    0.03 sec
      Start  2: test_c_symbols-c
 2/71 Test  #2: test_c_symbols-c ..................................   Passed    0.01 sec
      Start  3: test_batch_normalization_f32

Version: 1.7
OS: FreeBSD 12.2
clang-10

@yurivict yurivict added the sighting Suspicious library behavior. Should be promoted to a bug when confirmed label Nov 7, 2020
@emfomenk
Copy link

Hi @yurivict,

I wasn't able to reproduce the issue locally (using Linux though).
Tried 1, 2, 4, 8, and 16 threads in the thread-pool. Compiler: clang10.

Could you please run the test manually (DNNL_VERBOSE=2 ./tests/gtests/test_batch_normalization_f32) and share:

  1. on which test case it hangs,
  2. what is the call stack for at least one of the threads (hopefully it hangs in debug build as well),
  3. the verbose log as well.

Is the hang sporadic or persistent?

@vpirogov
Copy link
Member

Closing as we don't have enough information to reproduce the issue. Feel free to reopen with additional data.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
sighting Suspicious library behavior. Should be promoted to a bug when confirmed
Projects
None yet
Development

No branches or pull requests

3 participants