MaxGekk commented on a change in pull request #28244: 
[SPARK-31471][TESTS][BUILD] Add a python script to run multiple benchmarks 
URL: https://github.com/apache/spark/pull/28244#discussion_r410255326
 
 

 ##########
 File path: dev/run-benchmarks.py
 ##########
 @@ -0,0 +1,54 @@
+#!/usr/bin/env python3
+
+#
+# Licensed to the Apache Software Foundation (ASF) under one or more
+# contributor license agreements.  See the NOTICE file distributed with
+# this work for additional information regarding copyright ownership.
+# The ASF licenses this file to You under the Apache License, Version 2.0
+# (the "License"); you may not use this file except in compliance with
+# the License.  You may obtain a copy of the License at
+#
+#    http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+#
+
+import os
+from sparktestsupport.shellutils import run_cmd
+
+benchmarks = [
+    ['sql/test', 
'org.apache.spark.sql.execution.benchmark.AggregateBenchmark'],
 
 Review comment:
   > listing up files in some specific directories so we don't need to add here 
when we add a new benchmark if this targets to list up all benchmarks?
   
   I don't like this automation because I usually run sub-set of benchmarks and 
for me it is easier to just comment unneeded benchmarks in the script.

----------------------------------------------------------------
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:
[email protected]


With regards,
Apache Git Services

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to