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

jdk16 xLinux: cmdLineTester_pltest_j9sig_ext_0: Found zero nodes with memory even after NUMA was reported as supported #12433

Closed
andrew-m-leonard opened this issue Apr 14, 2021 · 5 comments

Comments

@andrew-m-leonard
Copy link
Contributor

https://ci.adoptopenjdk.net/job/Test_openjdk16_j9_extended.functional_x86-64_linux/61/consoleFull
node: test-docker-fedora33-x64-3
Build:

01:31:51  openjdk version "16" 2021-03-16
01:31:51  OpenJDK Runtime Environment AdoptOpenJDK-16+36-202104122343 (build 16+36-202104122343)
01:31:51  Eclipse OpenJ9 VM AdoptOpenJDK-16+36-202104122343 (build master-9b90f0a09, JRE 16 Linux amd64-64-Bit Compressed References 20210412_18 (JIT enabled, AOT enabled)
01:31:51  OpenJ9   - 9b90f0a09
01:31:51  OMR      - 440f0991d
01:31:51  JCL      - 073accb86d based on jdk-16+36)
03:22:40   [ERR] ----------------------------------------
03:22:40   [ERR] j9cuda tests
03:22:40   [ERR] ----------------------------------------
03:22:40   [ERR] 
03:22:40   [ERR] 
03:22:40   [ERR] Starting test basic
03:22:40   [ERR]   j9cuda: found 0 devices
03:22:40   [ERR] Ending test basic
03:22:40   [ERR] 
03:22:40   [ERR] Starting test errors
03:22:40   [ERR]   error 0: no error
03:22:40   [ERR]   error 38: no CUDA-capable device is detected
03:22:40   [ERR]   error -500: named symbol not found
03:22:40   [ERR] Ending test errors
03:22:40   [ERR] 
03:22:40   [ERR] Starting test invalid device identifiers
03:22:40   [ERR] Ending test invalid device identifiers
@andrew-m-leonard
Copy link
Contributor Author

@sxa fyi

@keithc-ca
Copy link
Contributor

That's normal output for the j9cuda test on a machine that doesn't have any GPUs.
The real issue is just below that:

[2021-04-13T02:22:40.813Z]  [ERR] FAILURES DETECTED. Number of failed tests: 1
[2021-04-13T02:22:40.813Z]  [ERR] 
[2021-04-13T02:22:40.813Z]  [ERR] 1: j9vmem_test_numa
[2021-04-13T02:22:40.813Z]  [ERR] 	../../../../../../openj9/runtime/tests/port/j9vmemTest.c line 1810: Found zero nodes with memory even after NUMA was reported as supported (FAIL)
[2021-04-13T02:22:40.813Z]  [ERR] 
[2021-04-13T02:22:40.813Z]  [ERR] 		LastErrorNumber: -252
[2021-04-13T02:22:40.813Z]  [ERR] 		LastErrorMessage: Unknown error -1

@keithc-ca keithc-ca changed the title jdk16 xLinux: cmdLineTester_pltest_j9sig_ext_0: no CUDA-capable device is detected jdk16 xLinux: cmdLineTester_pltest_j9sig_ext_0: Found zero nodes with memory even after NUMA was reported as supported Apr 14, 2021
@keithc-ca keithc-ca removed their assignment Apr 14, 2021
@pshipton
Copy link
Member

@sxa We looked at this before, but I don't find an OpenJ9 issue, maybe there is an issue in one of the Adopt/Adoptium repos. Seems to me I didn't want to change the test, and we decided it was a machine config problem?

@sxa
Copy link
Contributor

sxa commented Apr 14, 2021

This was the previous issue (Since Andrew had initially reported it as a CUDA failure I assumed it was something different)

@keithc-ca
Copy link
Contributor

Closing this as a duplicate of adoptium/aqa-tests#2143.

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

No branches or pull requests

4 participants