New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BEAM-210] Test that empty final panes are not produced. #211
Conversation
Add a test that we get an empty `ON_TIME` pane, and don't get the empty final pane when using accumulation mode with the only if non-empty `ClosingBehavior`.
LGTM |
// Trigger with 2 elements | ||
WindowMatchers.isSingleWindowedValue(containsInAnyOrder(1, 2), 1, 0, 10), | ||
// Trigger for the empty on time pane. | ||
WindowMatchers.isSingleWindowedValue(containsInAnyOrder(1, 2), 9, 0, 10))); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You said you couldn't repro the problem in the JIRA ticket, but this test seems to confirm exactly the WAI behavior.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was unable to repro the report of broken behavior. I was able to verify the WAI behavior.
LGTM, but do wait for travis as well. We have had a couple issues caught by only one or the other CI. |
I added a copy of this test with TRIGGER_ALWAYS. |
Add WindowedValue#explodeWindows
…lied-if [euphoria-core] make sure that windowBy() can be appliedIf()
Be sure to do all of the following to help us incorporate your contribution
quickly and easily:
[BEAM-<Jira issue #>] Description of pull request
mvn clean verify
. (Even better, enableTravis-CI on your fork and ensure the whole test matrix passes).
<Jira issue #>
in the title with the actual Jira issuenumber, if there is one.
Individual Contributor License Agreement.