# RFC: Future of Windows pre-commit CI

**URL:** <https://discourse.llvm.org/t/rfc-future-of-windows-pre-commit-ci/76840>\
**Category:** LLVM Project\
**Created:** [February 6, 2024, 8:45pm UTC](https://discourse.llvm.org/t/rfc-future-of-windows-pre-commit-ci/76840 "2024-02-06T20:45:11Z")\
**Posts on this page:** 1\
**Showing post:** 50

<div class="post-metadata">

**Author:** ![Endill](https://sea1.discourse-cdn.com/flex021/user_avatar/discourse.llvm.org/endill/32/13614_2.png) [@Endill](https://discourse.llvm.org/u/Endill)\
**Post date:** [February 17, 2024, 9:42pm UTC](https://discourse.llvm.org/t/rfc-future-of-windows-pre-commit-ci/76840/50 "2024-02-17T21:42:04Z")

</div>

> [@mehdi\_amini](#):
>
> I don’t quite see how splitting helps with anything: it’s quite the contrary actually.

It helps GitHub agents to not timeout and run out of disk space trying to build everything at once.

> [@mehdi\_amini](#):
>
> You can shard better the tests by running them on two machines: but this is aiming as gaining some latency at the cost of throughput (and my understanding is that we’re throughput limited here).

What I aim at personally is to address your concerns and get interim Windows CI enabled. Clang definitely feels unhealthiness of Windows CI for the past month, and we welcome any effort to improve the situation.

---

_[View the full topic](https://discourse.llvm.org/t/rfc-future-of-windows-pre-commit-ci/76840)._