You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@beam.apache.org by Apache Jenkins Server <je...@builds.apache.org> on 2017/02/02 19:14:34 UTC

Jenkins build became unstable: beam_PostCommit_Java_MavenInstall #2510

See <https://builds.apache.org/job/beam_PostCommit_Java_MavenInstall/2510/changes>

Jenkins build is back to stable : beam_PostCommit_Java_MavenInstall #2511

Posted by Apache Jenkins Server <je...@builds.apache.org>.

See <https://builds.apache.org/job/beam_PostCommit_Java_MavenInstall/2511/changes>

Re: Jenkins build became unstable: beam_PostCommit_Java_MavenInstall #2510

Posted by Kenneth Knowles <kl...@google.com.INVALID>.

The last time this occurred, it was because there's actually a
small-but-not-impossible chance that the expected output windows are not
saturated. We could do better by writing a manifest file as well or in the
near term just reduce the number of buckets things are randomly strewn into
or use a slightly larger example (exponential benefit per additional word).

On Thu, Feb 2, 2017 at 11:14 AM, Apache Jenkins Server <
jenkins@builds.apache.org> wrote:

> See <https://builds.apache.org/job/beam_PostCommit_Java_
> MavenInstall/2510/changes>
>
>

Re: Jenkins build became unstable: beam_PostCommit_Java_MavenInstall #2510

Posted by Jason Kuster <ja...@google.com.INVALID>.

Looks like a flake in WindowedWordCount -- listed change seems unrelated.

On Thu, Feb 2, 2017 at 11:14 AM, Apache Jenkins Server <
jenkins@builds.apache.org> wrote:

> See <https://builds.apache.org/job/beam_PostCommit_Java_
> MavenInstall/2510/changes>
>
>

-- 
-------
Jason Kuster
Apache Beam / Google Cloud Dataflow