[ 
https://issues.apache.org/jira/browse/BEAM-8575?focusedWorklogId=385648&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-385648
 ]

ASF GitHub Bot logged work on BEAM-8575:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 12/Feb/20 03:09
            Start Date: 12/Feb/20 03:09
    Worklog Time Spent: 10m 
      Work Description: bumblebee-coming commented on pull request #10835: 
[BEAM-8575] Removed MAX_TIMESTAMP from testing data
URL: https://github.com/apache/beam/pull/10835#discussion_r378019506
 
 

 ##########
 File path: sdks/python/apache_beam/transforms/util_test.py
 ##########
 @@ -551,9 +551,6 @@ def test_reshuffle_preserves_timestamps(self):
               {
                   'name': 'bar', 'timestamp': 33
               },
 
 Review comment:
   I'm afraid not.
   It seems b/146457921 and BEAM-9003 are two different issues.
   b/146457921 is for Unified Worker and BEAM-9003 is for Dataflow. 
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


Issue Time Tracking
-------------------

    Worklog Id:     (was: 385648)
    Time Spent: 49h 50m  (was: 49h 40m)

> Add more Python validates runner tests
> --------------------------------------
>
>                 Key: BEAM-8575
>                 URL: https://issues.apache.org/jira/browse/BEAM-8575
>             Project: Beam
>          Issue Type: Test
>          Components: sdk-py-core, testing
>            Reporter: wendy liu
>            Assignee: wendy liu
>            Priority: Major
>          Time Spent: 49h 50m
>  Remaining Estimate: 0h
>
> This is the umbrella issue to track the work of adding more Python tests to 
> improve test coverage.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to