-
Notifications
You must be signed in to change notification settings - Fork 57
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
caffe fork runtest failed #2
Comments
I tried to train it on imagenet, and the data layer failed to load lmdb. Any idea? |
lmdb test fixed by changing random_order in caffe.proto to |
Hello @ardiya , for the first question which is failure of unit test about DenseBlock, one strange part is there is the numbers on both sides seem to be large integers, so what is the order of instructions runned? And what is your environment? Thanks. |
Hi @Tongcheng, thanks for replying.
It is a float number, but there might be some problem when I copied it.
I clone it,
I am using Ubuntu 14.04.1 and this is the result of |
I encounter same problem when i run 12 FAILED TESTS |
I got the same problem. I think I did the same procedure as ardiya did. I cloned https://github.com/Tongcheng/caffe.git. Then, run removeCmakeDep.sh, mkdir build, cd build, cmake .., make -j4 and make runtest -j4. I am running Ubuntu 16.04, CUDA 8.0, cuDnn v5.1. |
Hi, @ardiya I suffer from similar problem, have you solved this? thanks. |
Hi, @Tongcheng @ardiya @zhimengfan1990 I meet the same problem while running 'make runtest', have you solved this? thanks. %% %% |
Hi, @zhangleiedu, I meet the same problem? have you solve this problem? thanks! 12 FAILED TESTS |
hello @ardiya @Tongcheng I meet exactly the same problem, have you solved it? Despite the unsettled problem, I still successfully trained my own model based on Dense_Block, but when I tested the model using python interface, it occured that: WARNING: Logging before InitGoogleLogging() is written to STDERR I just cannot figure out that why "caffe.LayerParameter" has no field named "denseblock_param" only during the test phase while trainning is ok? |
Hi, I want to post this in your caffe fork but there is no issue tab there.
So, I have tried to compile your latest caffe fork and encounter some failure when running `make runtest' there.
Do you have any suggestion? Perhaps something like revert to the stable commit or your DenseBlock_release1 will do?
The failure happen when testing DenseBlock layer and
and the data layer.
The text was updated successfully, but these errors were encountered: