!9IQChSjwSHXPPWTa:lix.systems

Lix

1106 Members
Lix user channel. Feel free to discuss on-topic issues here and give each other help. For matrix.to links to the rest of the Lix channels, see: https://wiki.lix.systems/books/lix-organisation/page/matrix-rooms296 Servers

Load older messages


SenderMessageTime
14 May 2024
@samrose:matrix.orgsamroseyou can't do that in a container in any case can you?00:48:22
@raitobezarius:matrix.orgraitobezariusOrthogonal, you can do it in a container, but it doesn't seem like Cirrus has a phase where you tell it "ok spawn me N containers and make them do this and that"00:49:07
@raitobezarius:matrix.orgraitobezariusThus it's necessarily serial inside of that container or you statically list all your targets as you change them00:49:28
@samrose:matrix.orgsamroseI see 00:49:30
@raitobezarius:matrix.orgraitobezariusPlus the container means you go from clean Nix store and you need to redownload stuff00:50:00
@raitobezarius:matrix.orgraitobezariusOr you need to build some hot container, push it to registry and load it in the CI00:50:14
@raitobezarius:matrix.orgraitobezariusWhereas current model share the Nix store and GC it as it go00:50:28
@samrose:matrix.orgsamroseso the optimal way would be to have the actual hardware, and be running nix-eval-jobs and just let nix do it's thing + retain the store basically like the way many people have used hydra in the past00:51:12
@raitobezarius:matrix.orgraitobezariusI'd say so, right now, an improvement would be to go to something like Hydra New Generation00:51:56
@samrose:matrix.orgsamroseit doesn't sound like it would be a lot of fun to maintain building this in containers the way you describe it00:52:00
@raitobezarius:matrix.orgraitobezarius
In reply to @samrose:matrix.org
it doesn't sound like it would be a lot of fun to maintain building this in containers the way you describe it
Hahahahahahaha :-)
00:52:13
@samrose:matrix.orgsamroseI mean, not that I think you are wrong at all00:52:25
@raitobezarius:matrix.orgraitobezariusOh, those are my 2 cents00:52:43
@raitobezarius:matrix.orgraitobezariusI may be wrong ofc00:52:48
@samrose:matrix.orgsamrosewhat you say makes sense given running nix-eval-jobs, and all of that00:53:16
@samrose:matrix.orgsamroseand it would be worth the effort to do Hydra New Generation00:53:29
@raitobezarius:matrix.orgraitobezariusBut it requires to improve Lix etc etc and then dogfood further and then Hydra Ng appears00:53:56
@samrose:matrix.orgsamroseyes first we would need to get the bugs and issues that are pending that makes sense00:54:39
@qyriad:katesiria.orgQyriad(we::Lix somewhat intentionally put ourselves in our own suffering path of CI)00:54:55
@raitobezarius:matrix.orgraitobezarius
In reply to @qyriad:katesiria.org
(we::Lix somewhat intentionally put ourselves in our own suffering path of CI)
(this is... our bootstrap path! :>)
00:55:17
@qyriad:katesiria.orgQyriadLix (and Nix) sucks at this, and it makes our lives worse. improving the state of the ecosystem will make our and everyone else's lives better00:55:22
@raitobezarius:matrix.orgraitobezarius
In reply to @samrose:matrix.org
yes first we would need to get the bugs and issues that are pending that makes sense
There's also some critical performance improvements on the scheduling side of things
00:55:36
@raitobezarius:matrix.orgraitobezariusMaybe my dumb view on this is I need to get an Ampere Altra Q80-30 somewhere, wire this up to gigabit (or even 100mbps) and then we get faster CI to some extent00:56:36
@raitobezarius:matrix.orgraitobezariusThen there's things like balancing out aarch64 capacity between Darwin and Linux00:56:54
@raitobezarius:matrix.orgraitobezariusThen there's things like improving scheduling as a whole00:57:16
@raitobezarius:matrix.orgraitobezariusEtc etc00:57:17
@samrose:matrix.orgsamrose
In reply to @raitobezarius:matrix.org
There's also some critical performance improvements on the scheduling side of things
here you are referring to the scheduling of ci builds is that right?
00:57:39
@raitobezarius:matrix.orgraitobezarius
In reply to @samrose:matrix.org
here you are referring to the scheduling of ci builds is that right?
More generally how a Nix aware CI component will decide to place a build on a piece of compute (policy, binpacking, etc.)
00:58:37
@raitobezarius:matrix.orgraitobezariusIt can be Nix scheduler, can be Hydra scheduler, there's multiple possible designs and paths 00:59:03
@samrose:matrix.orgsamrosehmm, so like you envision that this ci component might become part of nix or hydra I see00:59:12

There are no newer messages yet.


Back to Room ListRoom Version: 10