Skip to content
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-9557] Fix timer window boundary checking #11226

Merged
merged 3 commits into from
Apr 7, 2020

Conversation

reuvenlax
Copy link
Contributor

@steveniemitz
Copy link
Contributor

can we add a unit test to validate this behavior as well?

@amaliujia
Copy link
Contributor

Run Java PreCommit

@amaliujia
Copy link
Contributor

amaliujia commented Mar 26, 2020

This failed test might be relevant to this PR: org.apache.beam.sdk.transforms.ParDoTest$TimerTests.testOutOfBoundsEventTimeTimer

(link https://builds.apache.org/job/beam_PreCommit_Java_Phrase/1930/)

@reuvenlax
Copy link
Contributor Author

@amaliujia appears that test looks for specific strings in the exception (always a recipe for a brittle test). I changed "event time timer" to "event-time timer" which broke that test. Will fix.

@aaltay
Copy link
Member

aaltay commented Mar 27, 2020

@amaliujia appears that test looks for specific strings in the exception (always a recipe for a brittle test). I changed "event time timer" to "event-time timer" which broke that test. Will fix.

Agreed, it is brittle test.

@reuvenlax are you planning to fix the test, or could @amaliujia send a fixup commit here to change "event-time" to "event time"? This is only release blocking issue currently, I would like to unblock it sooner.

@reuvenlax
Copy link
Contributor Author

@aaltay fixing this now

@reuvenlax
Copy link
Contributor Author

@aaltay added new unit tests and fixed the broken one. However I'm noticing that test triggering seems broken on a number of PRs now. Is something wrong with the Jenkins master?

@aaltay
Copy link
Member

aaltay commented Mar 27, 2020

@aaltay added new unit tests and fixed the broken one. However I'm noticing that test triggering seems broken on a number of PRs now. Is something wrong with the Jenkins master?

Yes. Ongoing issue. @yifanzou is working on it. Repeating the test triggers a few times usually helps.

@reuvenlax
Copy link
Contributor Author

retest this please

2 similar comments
@reuvenlax
Copy link
Contributor Author

retest this please

@reuvenlax
Copy link
Contributor Author

retest this please

@reuvenlax
Copy link
Contributor Author

@steveniemitz tests added

@steveniemitz
Copy link
Contributor

looks great! These tests will be really helpful to ensure we don't have more regressions in the future. Thanks!

@reuvenlax
Copy link
Contributor Author

Run Java PreCommit

@reuvenlax
Copy link
Contributor Author

@aaltay Has part of this change already been merged to master? I notice that SimpleDoFnRunner.java at head already contains these changes, but the unit tests are not it.

@steveniemitz
Copy link
Contributor

it looks like #11252 was merged instead of this one.

@reuvenlax
Copy link
Contributor Author

reuvenlax commented Mar 29, 2020 via email

@amaliujia
Copy link
Contributor

LGTM

@amaliujia
Copy link
Contributor

@reuvenlax

do you need help on the failed java tests?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants