You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Beam JIRA Bot (Jira)" <ji...@apache.org> on 2020/08/02 17:07:02 UTC
[jira] [Commented] (BEAM-10328) IntegrationTest is flaky for
CurrentTime
[ https://issues.apache.org/jira/browse/BEAM-10328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17169586#comment-17169586 ]
Beam JIRA Bot commented on BEAM-10328:
--------------------------------------
This issue was marked "stale-assigned" and has not received a public comment in 7 days. It is now automatically unassigned. If you are still working on it, you can assign it to yourself again. Please also give an update about the status of the work.
> IntegrationTest is flaky for CurrentTime
> ----------------------------------------
>
> Key: BEAM-10328
> URL: https://issues.apache.org/jira/browse/BEAM-10328
> Project: Beam
> Issue Type: Improvement
> Components: dsl-sql-zetasql
> Reporter: Zijie Song
> Priority: P3
>
> Currently BeamSqlDateFunctionsIntegrationTest.testDateTimeFunctions_currentTime() is a flaky test, with following error message:
> * calSqlTransform/BeamCalcRel_18/ParDo(Calc)/ParMultiDo(Calc).output: null
> We cannot assert the currentTime casting are correct within 1 second.
> One way to solve this problem is to make a mock of system time by overriding the currentTime method and adding a way to set system time.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)