Apollo: Apollo 1.5 Build Error

Created on 23 Sep 2017  ·  12Comments  ·  Source: ApolloAuto/apollo

I've set up the docker environment in my Ubuntu. However when I ran the following command,
bash apollo.sh build
It gave me an error as an output:
ERROR: query interrupted
Can anyone give me some suggestions?
The full output is as follows:
`System check passed. Build continue ...
[WARNING] ESD CAN library supplied by ESD Electronics does not exist. If you need ESD CAN, please refer to third_party/can_card_library/esd_can/README.md.
Start building, please wait ...
INFO: Reading 'startup' options from /apollo/tools/bazel.rc: --batch_cpu_scheduling
Building: no action running
Building: no action running
Building: no action running
Building: no action running
Building: no action running
Building: no action running
Building: no action running
Building: no action running
Building: no action running
Building: no action running
Building: no action running
Building: no action running
Building: no action running
Building: no action running
Building: no action running
Building: no action running
Building: no action running
Building: no action running
Building: no action running
Building: no action running
Building: no action running
Building: no action running
Building: no action running
Building: no action running
Building: no action running
Building: no action running
Building: no action running
Building: no action running
Building: no action running
Building: no action running
Building: no action running
Building: no action running
Building: no action running
Building: no action running
Building: no action running
Building: no action running
Building: no action running
Building: no action running
Building: no action running
ERROR: query interrupted

[ERROR] Build failed!
[INFO] Took 2315 seconds
`

Build Enhancement

Most helpful comment

We met this issue in some bad networking environment, too.
It seems that bazel is trying to download dependencies but failed.

You can run "bazel query //..." first to see the procedure, and then continue to run "apollo.sh build".

All 12 comments

We met this issue in some bad networking environment, too.
It seems that bazel is trying to download dependencies but failed.

You can run "bazel query //..." first to see the procedure, and then continue to run "apollo.sh build".

Thanks for your fast reply. I'll try it again.

I cost a lost of to download "Building: no action running Fetching https://github.com/.../apollo-platform/releases/download/1.5.0/ros-indigo-apollo-1.5.0-x86_64.tar.gz;", do you have any package mirrors or agent to download these dependence ?

@fy2462 I had the same issue as yours. Hope others can help.

same, not working...

Thank you all for report!

It looks very slow to download tar ball from Github in China. We are working hard to release the pain.

the same problem.no action running...then failed.

@xiaoxq Is the problem solved?

For now you can still run "bazel query //..." first to see the dependency pulling progress. And then run "apollo.sh build".

We are thinking of hosting dependencies in docker image, and users in China could download image from docker-cn.com. It's promising, but sorry that we still need some time to verify technical and policy issue.

no action running...
have this problem been solved?

bash apollo.sh build

System check passed. Build continue ...
[WARNING] ESD CAN library supplied by ESD Electronics does not exist. If you need ESD CAN, please refer to third_party/can_card_library/esd_can/README.md.
[INFO] Start building, please wait ...
[INFO] bazel query
INFO: Reading 'startup' options from /apollo/tools/bazel.rc: --batch_cpu_scheduling

ERROR: query interrupted

[ERROR] Build failed in gen build targets!

[INFO] Took 55 seconds

Please help in resolving this error !

i tried running bazel query //... and the result is

INFO: Reading 'startup' options from /apollo/tools/bazel.rc: --batch_cpu_scheduling
ERROR: query interrupted
Building: no action running

Generally it's because of the slow data connection to pull dependencies from github. We have moved most stuffs into the docker image. Please sync your code and try again to see if it works.

Was this page helpful?
0 / 5 - 0 ratings