Chao Sun 4fe4b65d9e [SPARK-35315][TESTS] Keep benchmark result consistent between spark-submit and SBT ... ### What changes were proposed in this pull request? Set `IS_TESTING` to true in `BenchmarkBase`, before running benchmarks. ### Why are the changes needed? Currently benchmark can be done via 2 ways: `spark-submit`, or SBT command. However in the former Spark will miss some properties such as `IS_TESTING`, which is necessary to turn on/off certain behavior like codegen (`spark.sql.codegen.factoryMode`). Therefore, the result could differ between the two. In addition, the benchmark GitHub workflow is using the spark-submit approach. ### Does this PR introduce _any_ user-facing change? No ### How was this patch tested? N/A Closes #32440 from sunchao/SPARK-35315. Authored-by: Chao Sun <sunchao@apache.org> Signed-off-by: Yuming Wang <yumwang@ebay.com>		2021-05-05 18:30:51 +08:00
..
benchmarks	[SPARK-34950][TESTS] Update benchmark results to the ones created by GitHub Actions machines	2021-04-03 23:02:56 +03:00
src	[SPARK-35315][TESTS] Keep benchmark result consistent between spark-submit and SBT	2021-05-05 18:30:51 +08:00
pom.xml	[SPARK-34688][PYTHON] Upgrade to Py4J 0.10.9.2	2021-03-11 09:51:41 -06:00