-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
unit test stuck at memory test step #3687
Comments
Could be related to for (auto size :
{128, 256, 1024, 4096, 16384, 65536, 262144, 1048576, 4194304}) {
ps[paddle::memory::Alloc(gpu, size)] = size; in |
chenxi44 /paddle [develop ?] $ docker run -e WITH_GPU=OFF -v $PWD:/paddle paddle:dev
|
turned out to be my code base tested against old testing code within old docker dev image. delete and recreate build dir and rebuild dev docker image fixes the issue. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
#3676 (comment)
I was trying to run through the unit tests with CPU build in my local dev docker env, and it stuck at the memory_test step for over 20min or so. my docker set to use 6cores and 5G of memory. docker version Version 17.06.0-ce-mac19 (18663), running in Macbook pro.
74/134 Test #74: stringpiece_test .................... Passed 0.04 sec
Start 75: stringprintf_test
75/134 Test #75: stringprintf_test ................... Passed 0.04 sec
Start 76: to_string_test
76/134 Test #76: to_string_test ...................... Passed 0.04 sec
Start 77: memory_test
The text was updated successfully, but these errors were encountered: