Yicong-Huang commented on PR #58274: URL: https://github.com/apache/spark/pull/58274#issuecomment-5419425398
> **Proposal:** > > 1. Use `pyspark-periodic` to replace `pyspark-install`. > 2. Make `pyspark-periodic` run on all pre-merge CIs and all scheduled CIs, not just coverage. We are increasing some python version and architecture coverage for `test_install_spark` and `test_import_spark`, not reducing. The cost should not be too large. > > WDYT? My two cents: can we describe these groups based only on what they cover, rather than how/when they run? * pyspark-upstream: monitors changes in upstream libraries * pyspark-core: monitors changes related to PySpark installation This way, we can move them between scheduled/periodic CI, pre-merge CI, and post-merge CI without having to rename the groups. -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
