blaginin opened a new issue, #21241: URL: https://github.com/apache/datafusion/issues/21241
Sometimes we merge something only to later find out that extended tests are failing. Now that extended tests are fast, should we just move them into the normal checks and run per commit? The fundamental question is: do we have enough infra credits to run them on _every_ push (like we do with the normal tests). If we do - the change is trivial, just move the checks. If we don't, I think there's a smart solution - merge queues - https://github.com/apache/datafusion/issues/6880 We can have checks that only run when you're about to merge your PR. Some jobs (extended tests, mac os, etc.) would live there. The idea: - on every push - only run fast checks that actually matter - on merge - run everything (you don't have to wait either - GitHub will auto-merge your PR once all checks pass) I quite like the second approach, happy to discuss if anyone has opinions. -- 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]
