Shut down runner VM if startup fails (#11250) I was planning to do this as health check, which integrates with the actual MIG infrastructure, but that has ended up being a laborious process due to Google security rules and I still haven't gotten it to work. In the meantime, we've been having frequent issues with server errors from the GitHub actions control plane, which mean that the runners are never registered and the instances just sit around counting as "running" according to the autoscaler. This is a really simple method to just shut down the runners if setup fails. We should also add retries and stuff, but this works for now and should hopefully avoid us ending up with half our instance pool just sitting idle. Tested: I added a non-deterministic failure in the setup script (see reverted commit) and confirmed that some of the instances initially shut down, but eventually all came online as runners. skip-ci: Runner startup configuration not tested by CI.
IREE (Intermediate Representation Execution Environment, pronounced as “eerie”) is an MLIR-based end-to-end compiler and runtime that lowers Machine Learning (ML) models to a unified IR that scales up to meet the needs of the datacenter and down to satisfy the constraints and special considerations of mobile and edge deployments.
See our website for project details, user guides, and instructions on building from source.
IREE is still in its early phase. We have settled down on the overarching infrastructure and are actively improving various software components as well as project logistics. It is still quite far from ready for everyday use and is made available without any support at the moment. With that said, we welcome any kind of feedback on any communication channels!
See our website for more information.
IREE is licensed under the terms of the Apache 2.0 License with LLVM Exceptions. See LICENSE for more information.