You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 17, 2023. It is now read-only.
-- Could NOT find TENSORRT (missing: TENSORRT_INCLUDE_DIR TENSORRT_LIBRARY)
ERRORCannot find TensorRT library.
CMake Error: The following variables are used in this project, but they are set to NOTFOUND.
Please set them or make sure they are set and tested correctly in the CMake files:
/work/mxnet/3rdparty/onnx-tensorrt/TENSORRT_INCLUDE_DIR
used as include directory in directory /work/mxnet/3rdparty/onnx-tensorrt
used as include directory in directory /work/mxnet/3rdparty/onnx-tensorrt
used as include directory in directory /work/mxnet/3rdparty/onnx-tensorrt
used as include directory in directory /work/mxnet/3rdparty/onnx-tensorrt
used as include directory in directory /work/mxnet/3rdparty/onnx-tensorrt
used as include directory in directory /work/mxnet/3rdparty/onnx-tensorrt
-- Configuring incomplete, errors occurred!
See also "/work/mxnet/3rdparty/onnx-tensorrt/build/CMakeFiles/CMakeOutput.log".
See also "/work/mxnet/3rdparty/onnx-tensorrt/build/CMakeFiles/CMakeError.log".
TENSORRT_INCLUDE_DIR
used as include directory in directory /work/mxnet/3rdparty/onnx-tensorrt
used as include directory in directory /work/mxnet/3rdparty/onnx-tensorrt
used as include directory in directory /work/mxnet/3rdparty/onnx-tensorrt
used as include directory in directory /work/mxnet/3rdparty/onnx-tensorrt
used as include directory in directory /work/mxnet/3rdparty/onnx-tensorrt
used as include directory in directory /work/mxnet/3rdparty/onnx-tensorrt
used as include directory in directory /work/mxnet/3rdparty/onnx-tensorrt
used as include directory in directory /work/mxnet/3rdparty/onnx-tensorrt
used as include directory in directory /work/mxnet/3rdparty/onnx-tensorrt
used as include directory in directory /work/mxnet/3rdparty/onnx-tensorrt
used as include directory in directory /work/mxnet/3rdparty/onnx-tensorrt
used as include directory in directory /work/mxnet/3rdparty/onnx-tensorrt
used as include directory in directory /work/mxnet/3rdparty/onnx-tensorrt
used as include directory in directory /work/mxnet/3rdparty/onnx-tensorrt
used as include directory in directory /work/mxnet/3rdparty/onnx-tensorrt
TENSORRT_LIBRARY_INFER
linked by target "nvonnxparser_static" in directory /work/mxnet/3rdparty/onnx-tensorrt
linked by target "nvonnxparser" in directory /work/mxnet/3rdparty/onnx-tensorrt
linked by target "nvonnxparser_runtime" in directory /work/mxnet/3rdparty/onnx-tensorrt
linked by target "nvonnxparser_plugin" in directory /work/mxnet/3rdparty/onnx-tensorrt
linked by target "nvonnxparser_runtime_static" in directory /work/mxnet/3rdparty/onnx-tensorrt
TENSORRT_LIBRARY_INFER_PLUGIN
linked by target "nvonnxparser_static" in directory /work/mxnet/3rdparty/onnx-tensorrt
linked by target "nvonnxparser" in directory /work/mxnet/3rdparty/onnx-tensorrt
linked by target "nvonnxparser_runtime" in directory /work/mxnet/3rdparty/onnx-tensorrt
linked by target "nvonnxparser_plugin" in directory /work/mxnet/3rdparty/onnx-tensorrt
linked by target "nvonnxparser_runtime_static" in directory /work/mxnet/3rdparty/onnx-tensorrt
build.py: 2019-05-15 08:02:20,417Z INFO Waiting for status of container cc30cac8c8bd for 600 s.
build.py: 2019-05-15 08:02:22,337Z INFO Container exit status: {'Error': None, 'StatusCode': 1}
build.py: 2019-05-15 08:02:22,337Z ERROR Container exited with an error 😞
The text was updated successfully, but these errors were encountered:
Hey, this is the MXNet Label Bot.
Thank you for submitting the issue! I will try and suggest some labels so that the appropriate MXNet community members can help resolve it.
Here are my recommended labels: CI, Build
http://jenkins.mxnet-ci.amazon-ml.com/blue/organizations/jenkins/mxnet-validation%2Funix-gpu/detail/PR-14959/2/pipeline.
TensorRT build fails with:
The text was updated successfully, but these errors were encountered: