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
Error: (unix time) try if you are using GNU date #1993
Comments
If this is of any help, the same error can be obtained just by running the tests. I recompiled caffe to use cuDNN, and wanted to run the tests: obtained this: (I skipped all the passing tests before)
Anything I can do to help? |
I tried to start bisecting to identify where this bug could have come from but after a make clean and a reinstall, I can't reproduce anymore. |
Hi, Thanks for your help. Now, I have solved this problem. The problem is that the the format of train.txt file for generating the lmdb is in incorrect format. |
having same problem in caffe test when doing: make runtest [----------] 1 test from LayerFactoryTest/0, where TypeParam = N5caffe8FloatCPUE |
redid a: previous failed test ran OK but, this on failed: |
I am encountering the same problem when using IMAGE_DATA layers:
Compiling with |
anyone found a workaround ? |
+1 same issue here |
I did a bit of digging and it seems to me that this the "Error: (unix time) try if you are using GNU date" is unrelated to Caffe and the problem that you are encountering. See here, it appears this is just a result of the logging library (glog) that shows this when a failure happens. So all the problems that are posted here are unrelated. If you get this error, you should look at the stacktrace provided instead of the unix time thing. |
Hi guys, I have the same problem, someone managed to solve? |
@bunelr is quite right, there are many different unrelated errors here. The text which titles this issue is just a helpful hint for parsing the log message. You're welcome to open new tickets for specific, reproducible errors in |
I think most of this problem is due to the mis-use of cpu_data() mode and gpu_data() mode. I have encountered this problem while debugging something and I find that I should use cpu_data() instead of gpu_data(). The error is reasonable since the pointer to a gpu location doesn't mean anything in CPU. Data is in GPU. Hope this will help. |
I got the same error. But after the following steps, everything is good: |
I got this problem, because i use OpenBlas on Cents6.5,when i changed Atlas , make runtest successed. |
@ShijianTang , Hi |
I have this same issue - the SERIOUS one LayerFactoryTest/1.TestCreateLayer I am on cuda 7.5 on os/x |
I have the same issue |
I met the problem too. It's very confusing since the same network, if I use database1, everything is ok, but database2, the error occured. |
I was facing the same issue. Even though I recompiled the issue still exists. |
@sruthikesh-MU is right. It seems that the multiple GPUs trigger
|
@ShijianTang what was the issue with the train.txt format in your case? I fixed the same issue by fixing my |
@alexeystrakh How did you check your |
For me, the problem was caused by not assigning value to |
My OS is CentOS 7.4.1708 and Python is Anaconda 3 5.0.1.
My problem seems to be related to linker use the boost libraries under the Anaconda installation, e.g., /opt/anaconda3/lib. |
Hi! |
you are right! variables are used in CUDA_KERNEL_LOOP must be gpu_data(). However, if you make for() {} youself, you should keep corresponding variables as cpu_data(). Exciting! |
Come to the same problem with current version 04ab089 steps
trace
with gpu enabled
|
Any workarounds so far?
Interestingly enough, the final error is:
System: Mendel GNU / Linux (Eagle), 10.0 My solution:
Worked unbelievably miraculously well. No more random single errors in a few tests. All passed. No GNU time error.
|
Hi,
When I tried to train the model of bvlc_reference_caffenet by my own data set, I have a problem: can anyone tell me how to fix it?
The text was updated successfully, but these errors were encountered: