alamb commented on PR #13045: URL: https://github.com/apache/datafusion/pull/13045#issuecomment-2437768998
> if cargo nextest is supposed to work, are we also going to have CI guarantee that? That is an excellent question One way to do this would be to use nextest to run the tests, which might improve the CI speed (though we would have to pay for the time to build/install nextest itself) -- we actually do this in influxdb_iox and it works pretty well. In general I assume this is a developer convenience for a small number of developers, if it breaks as part of a subsequent PR we can also always fix it again and it won't affect other PRs. If these assumptions turn out to be untrue, we should reasses. Thus in my opinion adding adding a CI test would impose a burden that is not commensurate with the value that would be gained -- 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]
