-
Notifications
You must be signed in to change notification settings - Fork 30
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
Can't build project using Docker image #140
Comments
Hi Dmitriy, thanks for the detailed bug report. It's been a while since I've used the docker images but I'll have a go and see if I can reproduce locally. In the meantime, can you please confirm that your docker image has a working and stable internet connection? You could try something like:
Cheers, |
Hi Chris, thanks for replying. I tried the command, and it seems like internet connection is stable, I got index.html from wikipedia. Btw, when running bazel command, that was fetching packages, for a split second I could see that it was pulling them successfully, but getting stuck exactly on "@requirements". If you need more information or anything, I would be glad to provide :) |
Thanks for following up. The Some of the common causes are failures are:
What would be really helpful would be if you could try and install the packages in the docker environment yourself, using:
If the above succeeds, we know the error is with bazel. If it doesn’t succeed, the error message might help you figure out the root cause (especially if it's a missing dependency). If it isn't obvious what causes the error, post the full output here and I'll take a look. Cheers, |
Sadly, command above didn't fix the problem. It updated some packages, said that operation was successful, but running bazel lead to the same problem :( Thanks for the help, if I get an update to the situation - I will be sure to tell you. If there is anything else you know that might help - I would be glad to hear. Have a good one <3 |
Sorry to hear about this :( Yes, if Cheers, |
Thanks in advance :) |
@ChrisCummins I tried locally to build project on my mac. It seems like the problem is the same (I'm not really sure though), but I got more error output. Also I updated mac to Big Sur, but the problem was on previous Catalina as well. Before building I did type in
Here is the full output of running build command:
Here is the output of
|
Hi @Dender46, I'm sorry that I haven't got back to you yet, I've been extremely busy. The good news is that I have a workaround - basically, we can ignore the python dependencies with bazel and just use pip to manage them. This solves the spurious build errors like the one you are experiencing. It'll take a day or two to implement, but might not be for a while yet - I'm getting married tomorrow so will be offline for a week or two :) Cheers, |
Hey @ChrisCummins, congrats on your wedding! ❤️ 🥳 Hope you have a lovely honeymoon and few weeks off :) Congrats again! |
Hello @ChrisCummins! Happy holidays, hope you had a great time and happy New Year! How is it going? Have you been able to fix the problem? I'm currently too busy to fix it myself even if I knew how to do it, so I would highly appreciate your help. Cheers, |
Hi Dimitry, happy new year to you too :) Yes sorry about this, I have a fix, let me implement it tonight and get back to you. FWIW @fivosts has kindly volunteered to take over maintaining this project since I don't have the time to work on it these days, and he has done a great job in rewriting the build system to be a bit more user friendly. @fivosts , is that ready to merge? Cheers, |
When I try to do anything with bazel (for example run bazel build -c opt //deeplearning/clgen or bazel run //tools:whoami), it tries to fetch package '@requirements//' for 3 minutes, then gives up and throws error.
Trying to build project using Docker results in this weird error:
Here is the output from script ./tools/whoami.sh :
The text was updated successfully, but these errors were encountered: