[
https://issues.apache.org/jira/browse/AVRO-1887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16664004#comment-16664004
]
ASF GitHub Bot commented on AVRO-1887:
--------------------------------------
cutting commented on a change in pull request #353: AVRO-1887 Integrate Yetus
URL: https://github.com/apache/avro/pull/353#discussion_r228252518
##########
File path: build.sh
##########
@@ -54,25 +56,26 @@ do
# create interop test data
mkdir -p build/interop/data
- (cd lang/java/avro; mvn -P interop-data-generate generate-resources)
+ (cd lang/java/avro; mvn -B -P interop-data-generate generate-resources)
(cd lang/py; ant interop-data-generate)
(cd lang/c; ./build.sh interop-data-generate)
#(cd lang/c++; make interop-data-generate)
(cd lang/ruby; rake generate_interop)
(cd lang/php; ./build.sh interop-data-generate)
# run interop data tests
- (cd lang/java; mvn test -P interop-data-test)
+ (cd lang/java; mvn -B test -P interop-data-test)
(cd lang/py; ant interop-data-test)
(cd lang/c; ./build.sh interop-data-test)
#(cd lang/c++; make interop-data-test)
(cd lang/ruby; rake interop)
(cd lang/php; ./build.sh test-interop)
# java needs to package the jars for the interop rpc tests
- (cd lang/java; mvn package -DskipTests)
+ (cd lang/java; mvn -B package -DskipTests)
# run interop rpc test
- /bin/bash share/test/interop/bin/test_rpc_interop.sh
+ # This is not working for now
+ # /bin/bash share/test/interop/bin/test_rpc_interop.sh
Review comment:
Are all interop tests failing, or only a few? If only a few, I'd rather
disable just those.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> set up precommit checks via Apache Yetus
> ----------------------------------------
>
> Key: AVRO-1887
> URL: https://issues.apache.org/jira/browse/AVRO-1887
> Project: Avro
> Issue Type: Task
> Components: build, community
> Reporter: Sean Busbey
> Assignee: Suraj Acharya
> Priority: Blocker
> Attachments: AVRO-1887-0.patch, AVRO-1887-1.patch, AVRO-1887-2.patch
>
>
> The lack of automated checks for things like doing a full build is negatively
> impacting my ability to do timely reviews. We should leverage the work done
> by other communities and get precommit checks going with Apache Yetus ([ref
> Apache Yetus
> Precommit|http://yetus.apache.org/documentation/0.3.0/precommit-basic/])
> Yetus has built in support for using Docker as a containerized build
> environment ([ref
> docs|https://yetus.apache.org/documentation/0.3.0/precommit-advanced/#Docker_Support]),
> but I don't know if we can use the one we have directly or if we'll need to
> do some refactoring.
> Implementing this will ultimately require a committer (so that they can make
> changes to builds.apache.org), but a non-cmmitter can get the bulk of the
> work done by managing to do local yetus checks with the docker feature active.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
