-
Notifications
You must be signed in to change notification settings - Fork 594
Conversation
@@ -6,90 +6,90 @@ java_library( | |||
name = "aws-java-sdk", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the fix. In order for the travis ci to compile correctly, you need to download bazel 0.2.3 in the .travis.yml
https://github.com/twitter/heron/blob/master/.travis.yml
Can you make the changes and update the PR?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @kramasamy I have fixed this bug.
The Travis CI still not pass yet, I will get into the root of the matter to find out why.
@caofangkun - When I looked the log of travis ci, it seems to failing in pants. I was wondering if you could enable some logs so that we can identify why the error message is being issued. Based on @billonahill comments - I recommend add some debugging to see what file isn't being copied, or to set should_log to return True in tracer.py |
@caofangkun We've figured out that Bazel made some internal changes with handling Python scripts, which seem to have caused the travis failure. The following diff should fix this issue.
Additionally, the following modifications may be necessary.
|
I am also getting this warnings -
|
When I looked at the travis-ci logs, it seems to be failing with java tests and looking at each of the logs shows the following -
|
Since Bazel 0.2.3, Bazel warns if a cc rule's includes attribute points out of third_party |
Bazel team is working on this issue -- they might remove these warnings as well. |
For unit tests failure, it seems because of Bazel's change in java_test behavior since 0.2.1. |
@caofangkun Since Bazel's internal test structure changed, the pull from #938 (already merged to master) and the following changes are also necessary, which should resolve the unit test failures in Travis.
|
Hi @kramasamy @taishi8117 |
Awesome! The only issue remaining is the warnings which is not fixed even in bazel 0.3.0 |
Hi @kramasamy According to code of bazelbuild/bazel@f0a1884#diff-b1e05be607e9de9e40f306162531dc81R431 I did the following changes, and the warnings gone.
Should i fix this in this PR or file a new issue and fix it later? |
Please update bazel version for the website here too: And in the md files we should reference it via:
|
@@ -162,11 +162,11 @@ RUN \ | |||
ENV JAVA_HOME /usr/lib/jvm/java-8-oracle | |||
``` | |||
|
|||
#### Step 5 - An installation script for [Bazel](http://bazel.io/) version 0.1.2 or above. | |||
#### Step 5 - An installation script for [Bazel](http://bazel.io/) version 0.2.3 or above. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please update to use {{% bazelVersion %}}
here and below.
Hi @billonahill I have included your feedback in d74c1dc , Could you please have a review? |
@caofangkun - travis-ci seems to have failed. Can you please check? |
@kramasamy @caofangkun For the
|
Looking at the Travis failure message, I just realized that a similar error existed even from cc5da14, although Travis CI was successful for some reasons.
[Update] |
curl -O -L https://github.com/bazelbuild/bazel/releases/download/0.1.2/bazel-0.1.2-installer-darwin-x86_64.sh | ||
chmod +x bazel-0.1.2-installer-darwin-x86_64.sh | ||
./bazel-0.1.2-installer-darwin-x86_64.sh --user | ||
wget -O /tmp/bazel.sh https://github.com/bazelbuild/bazel/releases/download/{{% bazelVersion %}}/bazel-{{% bazelVersion %}}-installer-linux-x86_64.sh |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
s/linux/darwin/
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fixed.
Hi @taishi8117 , Thank you so much for your help, I have fixed it as you suggested. |
@caofangkun - can you update your branch since yours seems to have conflicts? |
@kramasamy I'm working on the conficts now, will fix it soon :) |
@caofangkun Thanks for fixing the conflicts. The Javadoc error might be resolved by merging #968 (already merged to master) --- can you try that? (and enable |
Thank you @taishi8117 After merge the CI passed now. |
Looks good to me! 👍 |
Looks great! |
@kramasamy What are the changes need to be made for our Twitter internal building/testing environment? |
Since Bazel Release 0.1.5 (2016-02-05)
"Repository rules must use names that are valid workspace names.", see: bazelbuild/bazel#874