manuzhang commented on code in PR #5939: URL: https://github.com/apache/datafusion-comet/pull/5939#discussion_r4013488168
########## .github/workflows/README.md: ########## @@ -15,14 +15,23 @@ Merging goes through GitHub's merge queue, configured by the `Merge Queue` ruleset in `.asf.yaml`. That splits CI into two tiers: - **PR tier** (`pr`): fast feedback while a change is being iterated on. - The Linux build, Spark 4.1 (catalyst and `sql_core` only) and Iceberg 1.11. -- **Queue tier** (`queue`): the authoritative gate. Everything the PR tier - runs, plus the macOS build, the benchmark compile check, the Spark 4.1 - `sql_hive` shards, Spark 3.5/4.0 and Iceberg 1.8/1.9/1.10, evaluated - against the merge result rather than against the PR head. + The Linux build, with the Comet test suites run against the default Spark + profile (4.1) only, and nothing else. +- **Queue tier** (`queue`): the authoritative gate. The Linux build with the + Comet test suites against every Spark profile, plus the macOS build, the + benchmark compile check, Spark 3.5/4.0/4.1 and Iceberg 1.8/1.9/1.10/1.11, + evaluated against the merge result rather than against the PR head. Every queue-only job has a `run-*` label that opts a pull request into it -early, listed in the diagram below. +early, listed in the diagram below. The PR tier used to be wider: Spark 4.1 Review Comment: I'm not sure we need such historical explanation in the README. -- 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]
