tustvold opened a new issue, #1833:
URL: https://github.com/apache/arrow-rs/issues/1833

   **Is your feature request related to a problem or challenge? Please describe 
what you are trying to do.**
   
   Since updating MIRI in #1828 it is periodically OOMing - 
https://github.com/apache/arrow-rs/actions/workflows/miri.yaml
   
   
![image](https://user-images.githubusercontent.com/1781103/173018511-f61ee955-f90a-467e-8666-f9e1f017d088.png)
   
   https://github.com/apache/arrow-rs/actions/runs/2473012537
   
   It has also been a long-time annoyance of mine that 
   **Describe the solution you'd like**
   
   I'm not entirely sure what the best course of action here is, rolling back 
to a 6 month old MIRI is not ideal and would require backing out changes in 
#1822, but then neither is having it randomly fail.
   
   It has been a long-time annoyance of mine that the the CI currently takes 
~40 minutes to chug through, despite significant caching. This is largely 
because the runners are rather piddly - 
https://docs.github.com/en/actions/using-github-hosted-runners/about-github-hosted-runners#supported-runners-and-hardware-resources.
 This also precludes automatically running any meaningful benchmarks (#1274). 
Perhaps we should invest some time into a more powerful CI system such as 
[buildkite](https://buildkite.com/apache-arrow) which is used by other arrow 
projects...
   
   **Describe alternatives you've considered**
   
   None
   


-- 
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]

Reply via email to