-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add a way to trigger the extended
test suite from a PR
#14319
Comments
This post might be useful for providing feedback on the status of the extended action being run. |
Posting a note to the PR saying "extended test suite ran {success_or_failure} on this PR" would be very cool too |
I've tested and put the results in testing section. After #14345 is merged, I can get the changes and it will be ready to merge imo. cc @alamb |
Ths came up again in the context of It would be great to figure out how to get this working |
Is your feature request related to a problem or challenge?
There is a great
extended
test suite that runs on each PR to main, https://github.com/apache/datafusion/blob/main/.github/workflows/extended.ymlIt doesn't run on PRs but does run on every commit to
main
as doing so consumes a significant amount of CI builder time and the jobs rarely fail. An example run is here: https://github.com/apache/datafusion/actions/runs/12987371654/job/36216118679Sometimes there are PRs (such as #13681 from @Rachelint ) where it would be really nice to verify that the extended suite still passes before we merge the PR to
main
Describe the solution you'd like
I would like some way to trigger the
extended
test suite from a PRDescribe alternatives you've considered
Maybe we could follow the model of
take
: https://github.com/apache/datafusion/blob/main/.github/workflows/take.ymlDescribed in
https://datafusion.apache.org/contributor-guide/index.html#open-contribution-and-assigning-tickets
So maybe we could make it so if someone added a comment like
To the PR the extended tests would also trigger
Additional context
No response
The text was updated successfully, but these errors were encountered: