That worked! INFO: Elapsed time: 758.221s, Critical Path: 168.57s INFO: 2565 processes: 2235 local, 330 worker. INFO: Build completed successfully, 4380 total actions
> On Nov 15, 2018, at 8:11 PM, Ning Wang <[email protected]> wrote: > > Agreed. > > For bazel, I think I manually download the specific version from > https://github.com/bazelbuild/bazel/releases and then install it. I > remember I upgraded and downgraded a few times but not very often. > > > > On Thu, Nov 15, 2018 at 2:26 PM Dave Fisher <[email protected]> wrote: > >> I am not sure how to get brew to give me the old version. I looked and do >> not see a way. >> >> So - more careful instructions next time. >> >> Regards, >> Dave >> >>> On Nov 15, 2018, at 2:13 PM, Ning Wang <[email protected]> wrote: >>> >>> bazel is not backward compatible. :( >>> >>> Plesae use 0.14.1 instead. >>> >>> This information is updated in the website source files a while ago but I >>> think it hasn't been deployed yet. It could be helpful to include this >>> information in the voting message next time. >>> >>> On Thu, Nov 15, 2018 at 11:26 AM Dave Fisher <[email protected]> >> wrote: >>> >>>> $ bazel version >>>> WARNING: Processed legacy workspace file >>>> >> /Users/davewave/Development/heron/incubator-heron-v-0.20.0-incubating-candidate-5/tools/bazel.rc. >>>> This file will not be processed in the next release of Bazel. Please >> read >>>> https://github.com/bazelbuild/bazel/issues/6319 for further >> information, >>>> including how to upgrade. >>>> Build label: 0.18.1-homebrew >>>> Build target: >>>> >> bazel-out/darwin-opt/bin/src/main/java/com/google/devtools/build/lib/bazel/BazelServer_deploy.jar >>>> Build time: Fri Nov 2 11:16:42 2018 (1541157402) >>>> Build timestamp: 1541157402 >>>> Build timestamp as int: 1541157402 >>>> >>>> >>>>> On Nov 15, 2018, at 11:23 AM, Ning Wang <[email protected]> wrote: >>>>> >>>>> Interesting. >>>>> >>>>> I am using 10.13 for my corp laptop. Will try at home. >>>>> >>>>> Which bazel version are you using? We are using 0.14.1. >>>>> >>>>> >>>>> >>>>> On Thu, Nov 15, 2018 at 11:07 AM Dave Fisher <[email protected]> >>>> wrote: >>>>> >>>>>> Hi - >>>>>> >>>>>> In testing and building the RC5 on macOS 10.14 I encountered some >>>> issues: >>>>>> >>>>>> $ bazel build --config=darwin heron/... >>>>>> WARNING: Processed legacy workspace file >>>>>> >>>> >> /Users/davewave/Development/heron/incubator-heron-v-0.20.0-incubating-candidate-5/tools/bazel.rc. >>>>>> This file will not be processed in the next release of Bazel. Please >>>> read >>>>>> https://github.com/bazelbuild/bazel/issues/6319 for further >>>> information, >>>>>> including how to upgrade. >>>>>> Starting local Bazel server and connecting to it... >>>>>> DEBUG: >>>>>> >>>> >> /private/var/tmp/_bazel_davewave/f2432422fcc701440a82a59536536f46/external/bazel_tools/tools/osx/xcode_configure.bzl:87:9: >>>>>> Invoking xcodebuild failed, developer dir: >>>>>> /Applications/Xcode8.app/Contents/Developer ,return code 256, stderr: >>>>>> Process terminated by signal 6, stdout: >>>>>> ERROR: >>>>>> >>>> >> /Users/davewave/Development/heron/incubator-heron-v-0.20.0-incubating-candidate-5/heron/api/src/java/BUILD:8:1: >>>>>> every rule of type java_doc implicitly depends upon the target >>>>>> '@local_jdk//:jdk-default', but this target could not be found because >>>> of: >>>>>> no such target '@local_jdk//:jdk-default': target 'jdk-default' not >>>>>> declared in package '' (did you mean 'jre-default'?) defined by >>>>>> >>>> >> /private/var/tmp/_bazel_davewave/f2432422fcc701440a82a59536536f46/external/local_jdk/BUILD.bazel >>>>>> ERROR: Analysis of target '//heron/api/src/java:heron-api-javadoc' >>>> failed; >>>>>> build aborted: Analysis failed >>>>>> INFO: Elapsed time: 9.642s >>>>>> INFO: 0 processes. >>>>>> FAILED: Build did NOT complete successfully (287 packages loaded) >>>>>> >>>>>> I have several versions of Xcode on my system and I am not sure why >>>> Bazel >>>>>> is choosing the older Xcode 8? >>>>>> >>>>>> I did >>>>>> $ bazel clean --expunge >>>>>> >>>>>> And now I’m getting different results. Any suggestions? >>>>>> >>>>>> Regards, >>>>>> Dave: >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>> >>>> >> >>
