beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (BEAM-1140) Apex ParDoBoundTranslatorTest.testMultiOutputParDoWithSideInputs is flaky
Date Tue, 03 Jan 2017 06:02:58 GMT


ASF GitHub Bot commented on BEAM-1140:

GitHub user tweise opened a pull request:

    [BEAM-1140] terminate stream in interval following the final mark to reduce test flakiness
(stop gap measure).

    Be sure to do all of the following to help us incorporate your contribution
    quickly and easily:
     - [ ] Make sure the PR title is formatted like:
       `[BEAM-<Jira issue #>] Description of pull request`
     - [ ] Make sure tests pass via `mvn clean verify`. (Even better, enable
           Travis-CI on your fork and ensure the whole test matrix passes).
     - [ ] Replace `<Jira issue #>` in the title with the actual Jira issue
           number, if there is one.
     - [ ] If this contribution is large, please file an Apache
           [Individual Contributor License Agreement](

You can merge this pull request into a Git repository by running:

    $ git pull BEAM-1140

Alternatively you can review and apply these changes as the patch at:

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1727
commit bb11170915f5c05629f591304f01fbc528e2ea57
Author: Thomas Weise <>
Date:   2017-01-03T05:58:57Z

    BEAM-1140 terminate stream in interval following the final mark to reduce test flakiness
(stop gap measure).


> Apex ParDoBoundTranslatorTest.testMultiOutputParDoWithSideInputs is flaky
> -------------------------------------------------------------------------
>                 Key: BEAM-1140
>                 URL:
>             Project: Beam
>          Issue Type: Bug
>          Components: runner-apex
>            Reporter: Eugene Kirpichov
>            Assignee: Thomas Weise
> The test fails about one in 10-20 times or so when run in "Run until failure" mode in
IntelliJ (I did it 3 times; once it failed on the 3rd run, once on the 15th, once on the 40th).
> It's making precommits unstable (e.g. currently
failed with this test error).
> Unfortunately I don't understand enough about the Apex runner to understand what's going
on and fix this myself...

This message was sent by Atlassian JIRA

View raw message