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

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

                Author: ASF GitHub Bot
            Created on: 25/Mar/20 19:40
            Start Date: 25/Mar/20 19:40
    Worklog Time Spent: 10m 
      Work Description: pabloem commented on pull request #11227: [BEAM-9601] 
Skip the streaming wordcount test because it uses a Python3.5.3+ feature
URL: https://github.com/apache/beam/pull/11227#discussion_r398120887
 
 

 ##########
 File path: 
sdks/python/apache_beam/runners/interactive/interactive_runner_test.py
 ##########
 @@ -150,9 +151,10 @@ def process(self, element):
     ]
     self.assertEqual(actual_reified, expected_reified)
 
+  @unittest.skipIf(
+      sys.version_info < (3, 6),
+      'InteractiveRunner has a minimum Python version of 3.5.3.')
 
 Review comment:
   should we skip if sys.version_info < 3,5,3? so we'll test on 3.5 if it's the 
right subversion?
 
----------------------------------------------------------------
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: 409760)
    Time Spent: 1h 10m  (was: 1h)

> Interactive test_streaming_wordcount failing
> --------------------------------------------
>
>                 Key: BEAM-9601
>                 URL: https://issues.apache.org/jira/browse/BEAM-9601
>             Project: Beam
>          Issue Type: Bug
>          Components: runner-py-interactive, test-failures
>            Reporter: Pablo Estrada
>            Assignee: Sam Rohde
>            Priority: Major
>          Time Spent: 1h 10m
>  Remaining Estimate: 0h
>




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

Reply via email to