| 10 Mar 2025 |
 Austin Horstman | Yeah, its just nice being able to run more builds simultaneously. Been setting up all my random computers as remote builders | 19:48:51 |
 Gaétan Lepage | Yes, my point is that it gets very easily overloaded.
Both darwin platforms rely on "only" 10 cores.
Often, python test suites will disregard whatever --cores value is used, and fill all the CPU cores.
This makes it very easy to completely freeze the system. | 19:50:04 |
 emily | more cores wouldn't improve that though, since such a package will overload any system it's built on | 20:15:12 |
| Gaétan Lepage | Yes, you are right. Besides this python test issue, more core would still help speeding up builds nonetheless. | 20:20:12 |
| Gaétan Lepage | * Yes, you are right. Besides this (very annoying) python test issue, more core would still help speeding up builds nonetheless. | 20:20:35 |
 Grimmauld (moving to @grimmauld:grapevine.grimmauld.de) | The builders are an amazing resource. It is much more enjoyable working with large builds or many rebuilds having some sort of offload system. I just recently got access, but its been great for working on Firefox (large build) or SDL (where often only transient dependents explode to changes in the includes/pkgconfig). Making testing faster and less painful is almost always a good thing. And so far I didn't have any issues with other people building at the same time at all. But I also don't build on Darwin. | 21:10:22 |
|  Gaël joined the room. | 22:08:20 |
| 11 Mar 2025 |
 Jonas Chevalier | I have to manually upload the invoices and running 2 months behind rn. I'll get it updated soon. | 09:02:54 |
| Jonas Chevalier | Yeah posting to Matrix would be a bit too noisy, but having those as metrics would be nice. | 09:05:06 |
