Re: Jenkins build became unstable: beam_PostCommit_Java_MavenInstall #2195

This was a manual invocation, which somehow causes an email to the commits list even though it was not run against master. Please ignore. Context: [BEAM-1194] On Wed, Dec 21, 2016 at 11:41 AM, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See

Re: Build failed in Jenkins: beam_PostCommit_MavenVerify #1823

This is why we want a submit queue / merge bot :) Dan On Tue, Nov 15, 2016 at 3:36 PM, Jean-Baptiste Onofré <j...@nanthrax.net> wrote: > Actually, the problem comes from the merge of MongoDB GridFS write. > > I'm fixing it. > > Sorry again. > > Regards > JB > > On 11/

Re: [jira] [Created] (BEAM-961) CountingInput could have starting number

Why not support this in a follow-on pardo that shifts the range? On Thu, Nov 10, 2016 at 1:22 PM, Kenneth Knowles (JIRA) wrote: > Kenneth Knowles created BEAM-961: > > > Summary: CountingInput could have starting number >

Re: incubator-beam git commit: fixup! spark pom.xml: limit parallelism in runnable-on-service tests

gt; Diff: http://git-wip-us.apache.org/repos/asf/incubator-beam/diff/f2637d74 > > Branch: refs/heads/spark-ros > Commit: f2637d74500bb33e6393ea446d49f2591dbe7632 > Parents: 6e1652a > Author: Dan Halperin <dhalp...@google.com> > Authored: Wed Nov 2 09:33:28 2016 -0700 > Committ

Re: Build failed in Jenkins: beam_PostCommit_RunnableOnService_SparkLocal #27

Sorry folks for the spam -- this is me playing around with the Spark postcommit seeing if it somehow magically passes after 2 months of idleness. I'll remove the email hook until I get it configured correctly. On Mon, Oct 17, 2016 at 2:49 PM, Apache Jenkins Server < jenk...@builds.apache.org>

Re: Jenkins build became unstable: beam_PostCommit_MavenVerify #1525

Filed https://issues.apache.org/jira/browse/BEAM-747 On Thu, Oct 13, 2016 at 5:33 PM, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See > >

Re: Jenkins build is back to stable : beam_PostCommit_MavenVerify » Apache Beam :: Examples :: Java #1503

Just an FYI that the issues here were legitimate issues in an external service that have since been resolved. They were present for approximately 90 minutes in a small set of places, and we were affected :) On Tue, Oct 11, 2016 at 7:37 PM, Apache Jenkins Server < jenk...@builds.apache.org> wrote:

Re: Jenkins build is still unstable: beam_PostCommit_RunnableOnService_GoogleCloudDataflow #1151

(filed https://issues.apache.org/jira/browse/BEAM-632) On Thu, Sep 15, 2016 at 12:14 AM, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See GoogleCloudDataflow/changes> > >

Re: Build failed in Jenkins: beam_PostCommit_RunnableOnService_GearpumpLocal #146

Sorry for the build spam everyone. I filed BEAM-598 about this, and I was able to fixed compilation but then I broken the runnable on service test suite. I think we need Manu's intervention to fix. For now, I've disabled the build. On Fri, Aug 26, 2016 at 5:53 PM, Apache Jenkins Server <

Re: Build failed in Jenkins: beam_PostCommit_PythonVerify #67

Filed JIRA: https://issues.apache.org/jira/browse/BEAM-441 On Mon, Jul 11, 2016 at 5:54 PM, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See > > > Changes: > > [dhalperi] Fix warnings that came with newly

Re: Jenkins build became unstable: beam_PostCommit_RunnableOnService_GoogleCloudDataflow #462

Looks like this was a transient failure in GCS (expected on occasion) that could/would have been resolved when the work item was retried. However, it looks like the test framework canceled the pipeline before that task was retried. Is this the desired behavior? Thanks, Dan On Wed, Jun 1, 2016 at

Re: Jenkins build is still unstable: beam_PostCommit_RunnableOnService_GoogleCloudDataflow #384

We're looking into these tests that have been failing for two days now. Luckily, they're not on the pre-commit path so they're not blocking work. On Fri, May 20, 2016 at 1:27 AM, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See < >

Re: Jenkins build is still unstable: beam_PostCommit_RunnableOnService_GoogleCloudDataflow #267

The first one of these failed because of a flake. This time, it looks like a test job was canceled? [link

Re: Jenkins build is still unstable: beam_PostCommit_RunnableOnService_GoogleCloudDataflow #225

This should be fixed now by a configuration change -- we recently made a package rename, and the config of this Jenkins build was not updated. On Tue, Apr 26, 2016 at 6:32 PM, Dan Halperin <dhalp...@google.com> wrote: > Looking > > On Tue, Apr 26, 2016 at 6:21 PM, Apache Jenkins

Re: Jenkins build is still unstable: beam_PostCommit_RunnableOnService_GoogleCloudDataflow #225

Looking On Tue, Apr 26, 2016 at 6:21 PM, Apache Jenkins Server < jenk...@builds.apache.org> wrote: > See < > https://builds.apache.org/job/beam_PostCommit_RunnableOnService_GoogleCloudDataflow/changes > > > >

Re: [jira] [Commented] (BEAM-190) Dead-letter drop for bad BigQuery records

I thought that we were under the impression that rather than losing data it's likely better to update your pipeline to handle these? On Wed, Apr 13, 2016 at 10:59 AM, Luke Cwik (JIRA) wrote: > > [ >

Re: [jira] [Commented] (BEAM-147) Rename Aggregator to [P]Metric

I'm concerned that we will rename it, then the new semantics we choose will result in a second rename. I agree with Davor that we should pin down the interface and semantics so we only do the rename once. On Fri, Mar 25, 2016 at 10:28 Robert Bradshaw (JIRA) wrote: > > [ >