Re: Build failed in Jenkins: beam_Release_NightlySnapshot #67

2016-06-09 Thread Jason Kuster
> to > org.apache.beam/beam-sdks-java-io-kafka/0.2.0-incubating-20160609.073312-3/beam-sdks-java-io-kafka-0.2.0-incubating-20160609.073312-3-javadoc.jar > No artifacts from beam_Release_NightlySnapshot » Apache Beam :: SDKs :: > Java :: IO :: Kafka #66 to compare, so performing full copy of artifacts > [JENKINS] Archiving < > https://builds.apache.org/job/beam_Release_NightlySnapshot/ws/sdks/java/maven-archetypes/starter/pom.xml> > to > org.apache.beam/beam-sdks-java-maven-archetypes-starter/0.2.0-incubating-SNAPSHOT/beam-sdks-java-maven-archetypes-starter-0.2.0-incubating-SNAPSHOT.pom > No artifacts from beam_Release_NightlySnapshot » Apache Beam :: SDKs :: > Java :: Maven Archetypes :: Starter #66 to compare, so performing full copy > of artifacts > [JENKINS] Archiving < > https://builds.apache.org/job/beam_Release_NightlySnapshot/ws/sdks/java/build-tools/pom.xml> > to > org.apache.beam/beam-sdks-java-build-tools/0.2.0-incubating-SNAPSHOT/beam-sdks-java-build-tools-0.2.0-incubating-SNAPSHOT.pom > [JENKINS] Archiving < > https://builds.apache.org/job/beam_Release_NightlySnapshot/ws/sdks/java/build-tools/target/beam-sdks-java-build-tools-0.2.0-incubating-SNAPSHOT.jar> > to > org.apache.beam/beam-sdks-java-build-tools/0.2.0-incubating-20160609.072701-3/beam-sdks-java-build-tools-0.2.0-incubating-20160609.072701-3.jar > [JENKINS] Archiving < > https://builds.apache.org/job/beam_Release_NightlySnapshot/ws/sdks/java/build-tools/target/beam-sdks-java-build-tools-0.2.0-incubating-SNAPSHOT-tests.jar> > to > org.apache.beam/beam-sdks-java-build-tools/0.2.0-incubating-20160609.072701-3/beam-sdks-java-build-tools-0.2.0-incubating-20160609.072701-3-tests.jar > No artifacts from beam_Release_NightlySnapshot » Apache Beam :: SDKs :: > Java :: Build Tools #66 to compare, so performing full copy of artifacts > [JENKINS] Archiving < > https://builds.apache.org/job/beam_Release_NightlySnapshot/ws/sdks/java/maven-archetypes/pom.xml> > to > org.apache.beam/beam-sdks-java-maven-archetypes-parent/0.2.0-incubating-SNAPSHOT/beam-sdks-java-maven-archetypes-parent-0.2.0-incubating-SNAPSHOT.pom > No artifacts from beam_Release_NightlySnapshot » Apache Beam :: SDKs :: > Java :: Maven Archetypes #66 to compare, so performing full copy of > artifacts > channel stopped > > -- --- Jason Kuster Apache Beam (Incubating) / Google Cloud Dataflow

Re: Jenkins build became unstable: beam_MavenVerify #14

2016-03-18 Thread Jason Kuster
the only commit was unrelated. >>> >>> On Thu, Mar 17, 2016 at 4:54 PM Apache Jenkins Server < >>> jenk...@builds.apache.org> wrote: >>> >>> > See <https://builds.apache.org/job/beam_MavenVerify/14/changes> >>> > >>> > >>> >> >> > -- --- Jason Kuster SETI - Cloud Dataflow

Re: PR failing Jenkins although tests are passing fine locally

2016-03-15 Thread Jason Kuster
information I may have missed. Thanks, Jason On Mon, Mar 14, 2016 at 12:19 PM, Amit Sela <amitsel...@gmail.com> wrote: > Jenkins seems satisfied now :) > > I guess "Use private Maven repository" property did the job ? > > Thanks, > > Amit > > On Mon, Mar 1

Re: PR failing Jenkins although tests are passing fine locally

2016-03-14 Thread Jason Kuster
>>>>>>> And Travis runs the same tests successfully... >>>>>>>>>> >>>>>>>>>> On Sun, Mar 13, 2016, 08:35 Davor Bonaci <da...@google.com.invalid >>>>>>>>>> >>>>>>>>> >>>>>>> wrote: >>>>>>>>> >>>>>>>>>> >>>>>>>>>> Jenkins jobs currently use "default Maven settings" and "default >>>>>>>>>>> >>>>>>>>>> Maven >>>>>>> >>>>>>>> global settings". We have some (limited) ability to view and >>>>>>>>>>> >>>>>>>>>> change >>>>>> >>>>>>> these >>>>>>>>> >>>>>>>>>> settings ourselves. >>>>>>>>>>> >>>>>>>>>>> Can we definitely confirm this is the root-cause? >>>>>>>>>>> >>>>>>>>>>> On Sat, Mar 12, 2016 at 8:49 AM, Amit Sela <amitsel...@gmail.com >>>>>>>>>>> >>>>>>>>>> >>>> wrote: >>>>>>>>> >>>>>>>>>> >>>>>>>>>>> I've issued PR https://github.com/apache/incubator-beam/pull/42 >>>>>>>>>>>> >>>>>>>>>>> and >>>>>>> >>>>>>>> while >>>>>>>>>>> >>>>>>>>>>>> Travis seems happy about it, Jenkis is not. >>>>>>>>>>>> >>>>>>>>>>>> Checking the build console >>>>>>>>>>>> https://builds.apache.org/job/beam_PreCommit/61/console I see >>>>>>>>>>>> >>>>>>>>>>> that >>>>>>> >>>>>>>> for >>>>>>>>> >>>>>>>>>> some >>>>>>>>>>>> reason it downloads MapR hadoop artifacts such as: >>>>>>>>>>>> >>>>>>>>>>>> [INFO] Downloading: >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>> >>> https://repository.jboss.org/nexus/content/repositories/releases/org/apache/hadoop/hadoop-client/2.7.0-mapr-1509/hadoop-client-2.7.0-mapr-1509.jar >>> >>>> >>>>>>>>>>>> instead of Apache Hadoop from Maven Central. >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> It seems that the issues causing the tests to fail are related >>>>>>>>>>>> >>>>>>>>>>> to >>>>>> >>>>>>> the >>>>>>>> >>>>>>>>> MapR distribution.. >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> Any reason for that ? How/Where does Jenkins configure it's >>>>>>>>>>>> >>>>>>>>>>> settings.xml ? >>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> Thanks, >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> Amit >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>> >>>> -- >>>> Jean-Baptiste Onofré >>>> jbono...@apache.org >>>> http://blog.nanthrax.net >>>> Talend - http://www.talend.com >>>> >>>> >>> >> > -- > Jean-Baptiste Onofré > jbono...@apache.org > http://blog.nanthrax.net > Talend - http://www.talend.com > -- --- Jason Kuster Cloud Dataflow/Apache Beam (incubating)

Re: Google donated Jenkins slaves

2016-03-29 Thread Jason Kuster
nal message > From: Daniel Takamori <p...@apache.org> > Date: 29/03/2016 07:58 (GMT+01:00) > To: dev@beam.incubator.apache.org > Subject: Google donated Jenkins slaves > > Hello Beam Devs! > Today I had a meeting a with Davor Bonaci and Jason Kuster from Google

Re: Testing resources are down

2016-05-02 Thread Jason Kuster
Root cause was an issue with the Puppet configuration for the slaves - the configuration issue has been fixed and the slaves have been relaunched. No future mitigation steps are necessary. On Mon, May 2, 2016 at 4:48 PM, Jason Kuster <jasonkus...@google.com> wrote: > Outage resolved. &

Beam Testing Guide on Website

2016-08-12 Thread Jason Kuster
/pull/37 Best, Jason -- --- Jason Kuster Apache Beam (Incubating) / Google Cloud Dataflow

FYI: All Runners Tested In Precommit

2016-09-15 Thread Jason Kuster
, Aljoscha, and Aviem for their help making this happen! Best, Jason -- --- Jason Kuster Apache Beam (Incubating) / Google Cloud Dataflow

Exploring Performance Testing

2016-10-17 Thread Jason Kuster
, particularly in other Apache projects. Anyone have any experience or thoughts? Best, Jason -- --- Jason Kuster Apache Beam (Incubating) / Google Cloud Dataflow

Re: Jenkins build is unstable: beam_PostCommit_RunnableOnService_GoogleCloudDataflow #1388

2016-10-21 Thread Jason Kuster
Filed https://issues.apache.org/jira/browse/BEAM-795 to track On Fri, Oct 21, 2016 at 6:08 AM, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See <https://builds.apache.org/job/beam_PostCommit_RunnableOnService_ > GoogleCloudDataflow/1388/> > > -- ---

Re: Hosting data stores for IO Transform testing

2016-11-27 Thread Jason Kuster
am not sure about > > >>> what > > >>> happens (or if the expected behavior depends on the runner), but well > > >>> maybe > > >>> it is just that I don’t know and we have tests to ensure this. > > >>> > > >>&g

Re: Build failed in Jenkins: beam_PostCommit_MavenVerify #1827

2016-11-15 Thread Jason Kuster
> MavenVerify/ws/sdks/pom.xml> to org.apache.beam/beam-sdks- > parent/0.4.0-incubating-SNAPSHOT/beam-sdks-parent-0.4. > 0-incubating-SNAPSHOT.pom > No artifacts from beam_PostCommit_MavenVerify » Apache Beam :: SDKs #1826 > to compare, so performing full copy of artifacts > [JENKINS] Archiving <https://builds.apache.org/job/beam_PostCommit_ > MavenVerify/ws/sdks/java/extensions/join-library/pom.xml> to > org.apache.beam/beam-sdks-java-extensions-join-library/ > 0.4.0-incubating-SNAPSHOT/beam-sdks-java-extensions- > join-library-0.4.0-incubating-SNAPSHOT.pom > [JENKINS] Archiving <https://builds.apache.org/job/beam_PostCommit_ > MavenVerify/ws/runners/pom.xml> to org.apache.beam/beam-runners- > parent/0.4.0-incubating-SNAPSHOT/beam-runners-parent- > 0.4.0-incubating-SNAPSHOT.pom > No artifacts from beam_PostCommit_MavenVerify » Apache Beam :: Runners > #1826 to compare, so performing full copy of artifacts > [JENKINS] Archiving <https://builds.apache.org/job/beam_PostCommit_ > MavenVerify/ws/sdks/java/io/jdbc/pom.xml> to org.apache.beam/beam-sdks- > java-io-jdbc/0.4.0-incubating-SNAPSHOT/beam-sdks-java-io- > jdbc-0.4.0-incubating-SNAPSHOT.pom > [JENKINS] Archiving <https://builds.apache.org/job/beam_PostCommit_ > MavenVerify/ws/sdks/java/extensions/pom.xml> to org.apache.beam/beam-sdks- > java-extensions-parent/0.4.0-incubating-SNAPSHOT/beam-sdks- > java-extensions-parent-0.4.0-incubating-SNAPSHOT.pom > [JENKINS] Archiving <https://builds.apache.org/job/beam_PostCommit_ > MavenVerify/ws/examples/pom.xml> to org.apache.beam/beam-examples- > parent/0.4.0-incubating-SNAPSHOT/beam-examples-parent- > 0.4.0-incubating-SNAPSHOT.pom > channel stopped > -- --- Jason Kuster Apache Beam (Incubating) / Google Cloud Dataflow

Performance Benchmarking Beam

2016-12-08 Thread Jason Kuster
://github.com/GoogleCloudPlatform/PerfKitBenchmarker [2] https://github.com/GoogleCloudPlatform/PerfKitBenchmarker/pull/1214 [3] https://github.com/jasonkuster/PerfKitBenchmarker/tree/beam Looking forward to moving forward with this. Jason -- --- Jason Kuster Apache Beam (Incubating) / Google

Re: Jenkins build is still unstable: beam_PostCommit_Java_RunnableOnService_Dataflow #1787

2016-12-10 Thread Jason Kuster
Jenkins Server < jenk...@builds.apache.org> wrote: > See <https://builds.apache.org/job/beam_PostCommit_Java_ > RunnableOnService_Dataflow/changes> > > -- --- Jason Kuster Apache Beam (Incubating) / Google Cloud Dataflow

Re: Jenkins build is still unstable: beam_PostCommit_Java_RunnableOnService_Dataflow #1788

2016-12-10 Thread Jason Kuster
Commit_Java_ > RunnableOnService_Dataflow/1788/> > > -- --- Jason Kuster Apache Beam (Incubating) / Google Cloud Dataflow

Re: Jenkins build is still unstable: beam_PostCommit_Java_RunnableOnService_Dataflow #1805

2016-12-13 Thread Jason Kuster
ervice_Dataflow/changes> > > -- --- Jason Kuster Apache Beam (Incubating) / Google Cloud Dataflow

Re: Jenkins build is still unstable: beam_PostCommit_Java_MavenInstall #2066

2016-12-11 Thread Jason Kuster
Filed https://issues.apache.org/jira/browse/BEAM-1130 for breaks here and in spark RoS tests On Sun, Dec 11, 2016 at 5:00 PM, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See <https://builds.apache.org/job/beam_PostCommit_Java_ > MavenInstall/changes> >

Re: Jenkins build is still unstable: beam_PostCommit_Java_RunnableOnService_Spark #385

2016-12-11 Thread Jason Kuster
Filed https://issues.apache.org/jira/browse/BEAM-1130 On Sun, Dec 11, 2016 at 4:52 PM, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See <https://builds.apache.org/job/beam_PostCommit_Java_ > RunnableOnService_Spark/changes> > > -- --- Jason Kuster

Re: Jenkins build became unstable: beam_PostCommit_RunnableOnService_GoogleCloudDataflow #1690

2016-11-30 Thread Jason Kuster
Same issue Kenn is investigating with MavenVerify. On Wed, Nov 30, 2016 at 3:28 PM, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See <https://builds.apache.org/job/beam_PostCommit_RunnableOnService_ > GoogleCloudDataflow/1690/changes> > > -- ---

FYI: Jenkins Job Changes

2016-11-30 Thread Jason Kuster
names are changing to clarify what's going on, but otherwise everything should be staying the same. I've updated the jobs and am tracking down a couple of failures (coveralls token got removed by accident, for example). Follow the jira for up-to-date state. Jason -- --- Jason Kuster Apache Beam

Re: Jenkins precommit worker affinity

2016-12-01 Thread Jason Kuster
gle.com.invalid> > wrote: > >> It appears that the new job beam_PreCommit_Java_MavenInstall has an >> affinity for Jenkins worker beam3 while workers beam1 and beam2 sit idle. >> Is this intentional? There seems to be a backlog of half a dozen builds. >> > > -- --- Jason Kuster Apache Beam (Incubating) / Google Cloud Dataflow

Re: Build failed in Jenkins: beam_PostCommit_Java_RunnableOnService_Spark #513

2016-12-20 Thread Jason Kuster
ugins.gitclient.RemoteGitImpl$ > CommandInvocationHandler$1.call(RemoteGitImpl.java:152) > at org.jenkinsci.plugins.gitclient.RemoteGitImpl$ > CommandInvocationHandler$1.call(RemoteGitImpl.java:145) > at hudson.remoting.UserRequest.perform(UserRequest.java:153) > at hudson.remoti

Re: Jenkins build became unstable: beam_PostCommit_Java_MavenInstall #2185

2016-12-20 Thread Jason Kuster
https://issues.apache.org/jira/browse/BEAM-1067 On Tue, Dec 20, 2016 at 3:52 PM, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See <https://builds.apache.org/job/beam_PostCommit_Java_ > MavenInstall/2185/changes> > > -- --- Jason Kuster Apache Be

Re: Build failed in Jenkins: beam_PostCommit_Java_RunnableOnService_Apex #83

2016-12-21 Thread Jason Kuster
rRequest.perform(UserRequest.java:153) > at hudson.remoting.UserRequest.perform(UserRequest.java:50) > at hudson.remoting.Request$2.run(Request.java:332) > at hudson.remoting.InterceptingExecutorService$1.call( > InterceptingExecutorService.java:68) > at java.util.concurrent.FutureTask.run(FutureTask.java:262) > at java.util.concurrent.ThreadPoolExecutor.runWorker( > ThreadPoolExecutor.java:1145) > at java.util.concurrent.ThreadPoolExecutor$Worker.run( > ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:745) > at ..remote call to beam1(Native Method) > at hudson.remoting.Channel.attachCallSiteStackTrace( > Channel.java:1416) > at hudson.remoting.UserResponse.retrieve(UserRequest.java:253) > at hudson.remoting.Channel.call(Channel.java:781) > at org.jenkinsci.plugins.gitclient.RemoteGitImpl$ > CommandInvocationHandler.execute(RemoteGitImpl.java:145) > at sun.reflect.GeneratedMethodAccessor761.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke( > DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.jenkinsci.plugins.gitclient.RemoteGitImpl$ > CommandInvocationHandler.invoke(RemoteGitImpl.java:131) > at com.sun.proxy.$Proxy91.execute(Unknown Source) > at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:797) > ... 11 more > ERROR: null > > -- --- Jason Kuster Apache Beam (Incubating) / Google Cloud Dataflow