9 ms·
IIRC one of the major factors holding back M3 support was the lack of a M3 mini for use in their CI environment. Now that there's an M4 mini hopefully there are
by quux 2y ago
IIRC one of the major factors holding back M3 support was the lack of a M3 mini for use in their CI environment. Now that there's an M4 mini hopefully there aren't any obstacles to them adding M4 support
- mmcnl 2y agoWhy would that matter? You can use a MacBook in CI too?
- School-Cotton 2y agoHow? What cloud providers offer it? MacStadium and AWS don't. I guess you could have a physical MBP in your house and connect it to some bring-your-own-infrastructure CI setup, but most people wouldn't want to do that.
- mmcnl 2y agoI meant using a physical device indeed.
- wtallis 2y agoCloud providers don't seem too relevant to a discussion of CI for kernel and driver development.
- School-Cotton 2y agoWhy not?
- wtallis 2y agoHow do you imagine that a cloud computing platform designed around running Macs with macOS would work for testing an entirely different OS running on bare metal on hardware that doesn't have a BMC, and usefully catching and logging frequent kernel panics and failed boots? It's a pretty hard problem to partially automate for setups with an engineer in the room. It doesn't sound at all feasible for an unattended data center setup that's designed to host Xcode for compiling apps under macOS.
- manmal 2y agoGitHub’s self hosted runners are as painless as they can get, and the Mac Mini in my basement is way faster than their hosted offering.
- chippiewill 2y agoGetting M4 Mac Mini CI might be a while considering the amount they've changed the package. Too tall to go into a 1U, smaller so the rack frames need to be redesigned. Power button now on the bottom so switch actuation need finagling.