tensorflow / tensorflow

An Open Source Machine Learning Framework for Everyone
https://tensorflow.org
Apache License 2.0
186.07k stars 74.27k forks source link

Unable to build #35431

Closed JesterOrNot closed 4 years ago

JesterOrNot commented 4 years ago

Please make sure that this is a build/installation issue. As per our GitHub Policy, we only address code/doc bugs, performance issues, feature requests and build/installation issues on GitHub. tag:build_template

System information

Describe the problem

Provide the exact sequence of commands / steps that you executed before running into the problem After about 20+ minutes of watching the code build the build stopped abruptly

Any other info / logs Here is a link to an enviorment where you can run my exact dev-env in the cloud https://gitpod.io/#https://github.com/JesterOrNot/tensorflow/tree/JesterOrNot/gitpod-setup

./tensorflow/python/lib/core/pybind11_proto.h:40:44: warning: 'pybind11::str pybind11::detail::object_api<Derived>::str() const [wi
th Derived = pybind11::handle]' is deprecated: Use py::str(obj) instead [-Wdeprecated-declarations]
       std::string(py_object.get_type().str()), " is not a valid proto."));
                                            ^
In file included from external/pybind11/include/pybind11/cast.h:13,
                 from external/pybind11/include/pybind11/attr.h:13,
                 from external/pybind11/include/pybind11/pybind11.h:49,
                 from tensorflow/python/client/device_lib_wrapper.cc:18:
external/pybind11/include/pybind11/pytypes.h:147:19: note: declared here
     pybind11::str str() const;
                   ^~~
INFO: From Compiling tensorflow/stream_executor/stream_executor_pimpl.cc [for host]:
tensorflow/stream_executor/stream_executor_pimpl.cc: In member function 'stream_executor::DeviceMemoryBase stream_executor::StreamE
xecutor::Allocate(tensorflow::uint64, tensorflow::int64)':
tensorflow/stream_executor/stream_executor_pimpl.cc:462:31: warning: comparison of integer expressions of different signedness: 'lo
ng long unsigned int' and 'tensorflow::int64' {aka 'long long int'} [-Wsign-compare]
       mem_alloc_bytes_ + size > memory_limit_bytes_) {
       ~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~
In file included from ./tensorflow/core/platform/default/logging.h:29,
                 from ./tensorflow/core/platform/logging.h:27,
                 from ./tensorflow/core/platform/status.h:24,
                 from ./tensorflow/core/platform/errors.h:22,
                 from ./tensorflow/core/lib/core/errors.h:19,
                 from ./tensorflow/stream_executor/device_memory_allocator.h:23,
                 from ./tensorflow/stream_executor/stream_executor_pimpl.h:28,
                 from tensorflow/stream_executor/stream_executor_pimpl.cc:20:
./tensorflow/core/platform/default/logging.h: In instantiation of 'std::__cxx11::string* tensorflow::internal::Check_EQImpl(const T1&, const T2&, const char*) [with T1 = int; T2 = long long unsigned int; std::__cxx11::string = std::__cxx11::basic_string<char>]':
tensorflow/stream_executor/stream_executor_pimpl.cc:700:3:   required from here
./tensorflow/core/platform/default/logging.h:386:25: warning: comparison of integer expressions of different signedness: 'const int' and 'const long long unsigned int' [-Wsign-compare]
                         ==)  // Compilation error with CHECK_EQ(NULL, x)?
./tensorflow/core/platform/macros.h:88:49: note: in definition of macro 'TF_PREDICT_TRUE'
 #define TF_PREDICT_TRUE(x) (__builtin_expect(!!(x), 1))
                                                 ^
./tensorflow/core/platform/default/logging.h:385:1: note: in expansion of macro 'TF_DEFINE_CHECK_OP_IMPL'
 TF_DEFINE_CHECK_OP_IMPL(Check_EQ,
 ^~~~~~~~~~~~~~~~~~~~~~~
INFO: From Compiling tensorflow/compiler/mlir/tensorflow/utils/tpu_rewrite_device_util.cc [for host]:
tensorflow/compiler/mlir/tensorflow/utils/tpu_rewrite_device_util.cc: In function 'tensorflow::Status tensorflow::{anonymous}::GetT
PUDevices(tensorflow::Devices, llvm::ArrayRef<tensorflow::DeviceNameUtils::ParsedName>, llvm::SmallVectorImpl<llvm::SmallVector<ten
sorflow::DeviceNameUtils::ParsedName, 8> >*)':
tensorflow/compiler/mlir/tensorflow/utils/tpu_rewrite_device_util.cc:129:27: warning: comparison of integer expressions of differen
t signedness: 'int' and 'size_t' {aka 'long unsigned int'} [-Wsign-compare]
     if (num_tpus_per_host != host_tpu_devices.size())
         ~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~
INFO: From Compiling tensorflow/core/kernels/quantization_utils.cc [for host]:
In file included from external/gemmlowp/public/../internal/dispatch_gemm_shape.h:23,
                 from external/gemmlowp/public/gemmlowp.h:19,
                 from ./tensorflow/core/kernels/quantization_utils.h:37,
                 from tensorflow/core/kernels/quantization_utils.cc:16:
external/gemmlowp/public/../internal/multi_thread_gemm.h: In member function 'void gemmlowp::WorkersPool::LegacyExecuteAndDestroyTa
sks(const std::vector<gemmlowp::Task*>&)':
external/gemmlowp/public/../internal/multi_thread_gemm.h:405:23: warning: comparison of integer expressions of different signedness
: 'int' and 'std::size_t' {aka 'long unsigned int'} [-Wsign-compare]
     for (int i = 0; i < tasks_count - 1; i++) {
                     ~~^~~~~~~~~~~~~~~~~
In file included from tensorflow/core/kernels/quantization_utils.cc:16:
./tensorflow/core/kernels/quantization_utils.h: In function 'void tensorflow::RequantizeManyInNewRangeReference(const qint32*, tensorflow::int64, float, float, float, float, tensorflow::quint8*)':
./tensorflow/core/kernels/quantization_utils.h:271:32: warning: comparison of integer expressions of different signedness: 'size_t' {aka 'long unsigned int'} and 'tensorflow::int64' {aka 'long long int'} [-Wsign-compare]
   for (size_t index = 0; index < count; ++index) {
                          ~~~~~~^~~~~~~
[6,434 / 12,032] 16 actions running
    Compiling tensorflow/python/tfe_wrapper.cc [for host]; 77s local
    Compiling tensorflow/core/kernels/rnn/lstm_ops.cc [for host]; 44s local
    Compiling tensorflow/core/kernels/rnn/gru_ops.cc [for host]; 43s local
    Compiling tensorflow/stream_executor/stream.cc [for host]; 41s local
    Compiling tensorflow/core/kernels/split_lib_cpu.cc [for host]; 28s local
    Compiling .../core/kernels/serialize_sparse_op.cc [for host]; 24s local
    //tensorflow/core/kernels:deserialize_sparse_string_op; 22s local
    Compiling .../core/kernels/sparse_reorder_op.cc [for host]; 22s local ...

Server terminated abruptly (error code: 14, error message: 'Socket closed', log file: '/home/gitpod/.cache/bazel/_bazel_gitpod/2c92b5569ddded7b3a6bd5e139451b60/server/jvm.out'
mihaimaruseac commented 4 years ago

Looks like your cloud instance closed connection, not an issue of TF itself.

Gaurav7004 commented 4 years ago

please try once with older versions of python...

ravikyram commented 4 years ago

@JesterOrNot Any update on the issue please. Thanks!

JesterOrNot commented 4 years ago

@Gubarev What python version do you mean?

Gubarev commented 4 years ago

@Gubarev What python version do you mean?

@JesterOrNot Seems like I was mentioned by mistake and I think this question should be addressed to @Gaurav7004 :)

JesterOrNot commented 4 years ago

@Gaurav7004 What python version do you mean? Also sorry @Gubarev

ymodak commented 4 years ago

Is this still an issue? Not sure if you are trying to build tf from prebuilt binary or from source. In case of building from source can you please try by lowering your bazel version to 0.26.1 https://github.com/tensorflow/tensorflow/blob/a641fa1c5c10f0a278c7671fd6f7df550a74935d/configure.py#L53

JesterOrNot commented 4 years ago

I am building it from the source I will test with those modifications.

JesterOrNot commented 4 years ago

image

mihaimaruseac commented 4 years ago

Make sure you have the right bazel version. Please run ./configure

ymodak commented 4 years ago

Automatically closing due to lack of recent activity. Please update the issue when new information becomes available, and we will reopen the issue. Thanks!

google-ml-butler[bot] commented 4 years ago

Are you satisfied with the resolution of your issue? Yes No