blaginin opened a new pull request, #22923: URL: https://github.com/apache/datafusion/pull/22923
@gmcdonald has rolled back the runs-on app so we can get faster CI back, and also reduce the burden on GitHub Actions: https://github.com/apache/datafusion/issues/22455 I was hoping to just switch the `USE_RUNS_ON` flag in the settings, but it turns out forks have no access to upstream env variables, even if they are not secrets. That means if runs-on is ever disabled again, we'll need to revert the revert... Or maybe we can have a check at the beginning of each CI run that reads some config flag / checks whether runs-on is available, and decides where to schedule the rest. I don't mind doing either. Curious what others think? Maybe an auto CI check to make this more automated? Happy to do that on top. -- 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]
