Jefffrey opened a new issue, #11469: URL: https://github.com/apache/arrow-rs/issues/11469
https://github.com/apache/arrow-rs/pull/11097 introduced merge queues, and moved some workflows to only run in the queue, for example miri. This ensures we run it only once, meaning we burn much less compute overall: previously we ran on main and on each PR update, now we run once per PR merge. Consider moving other jobs from running on each PR update and be like miri and run only in merge queue. Looking mainly at: - archery integration test: this takes 18 minutes on average, and i dont expect it to fail often enough to warrant needing to run on each PR update 🤔 - separately we could look into optimizing this job as a whole; for example it takes about 13 minutes just to setup and build the arrows we're testing against, can we using caching to some degree here? - windows tests: similarly, not sure how often this would fail and it takes about 9 min Related issue: - https://github.com/apache/arrow-rs/issues/11331 -- 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]
