[GitHub] [beam] dmvk commented on a change in pull request #12030: [BEAM-10270] Disable Pardo test with 200 iterations on Flink

[GitBox <gi...@apache.org>]

dmvk commented on a change in pull request #12030:
URL: https://github.com/apache/beam/pull/12030#discussion_r443618694



##########
File path: .test-infra/jenkins/job_LoadTests_ParDo_Flink_Python.groovy
##########
@@ -79,29 +79,31 @@ def batchScenarios = { datasetName -> [
                         environment_type     : 'DOCKER',
                 ]
         ],
-        [
-                title          : 'ParDo Python Load test: 20M 100 byte records 200 times',
-                test           : 'apache_beam.testing.load_tests.pardo_test',
-                runner         : CommonTestProperties.Runner.PORTABLE,
-                pipelineOptions: [
-                        job_name             : 'load-tests-python-flink-batch-pardo-2-' + now,
-                        project              : 'apache-beam-testing',
-                        publish_to_big_query : true,
-                        metrics_dataset      : datasetName,
-                        metrics_table        : 'python_flink_batch_pardo_2',
-                        influx_measurement   : 'python_batch_pardo_2',
-                        input_options        : '\'{' +
-                                '"num_records": 20000000,' +
-                                '"key_size": 10,' +
-                                '"value_size": 90}\'',
-                        iterations           : 200,
-                        number_of_counter_operations: 0,
-                        number_of_counters   : 0,
-                        parallelism          : 5,
-                        job_endpoint         : 'localhost:8099',
-                        environment_type     : 'DOCKER',
-                ]
-        ],
+// TODO(BEAM-10270): Takes too long time to execute (currently more than 2 hours). Re-enable

Review comment:
       @mxm Sorry, back from vacation.
   
   Unfortunatelly I'm not really familiar with the portable runner. I guess that some of the recent  "legacy" batch runner changes may have affected the portable runner too, but it's hard to say.
   
   Can you `git bisect` to a commit that introduces the regression?




----------------------------------------------------------------
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:
users@infra.apache.org