orivej has joined #nixos-borg
orivej has quit [Ping timeout: 276 seconds]
orivej has joined #nixos-borg
jtojnar has quit [Ping timeout: 260 seconds]
jtojnar has joined #nixos-borg
orivej has quit [Ping timeout: 264 seconds]
orivej has joined #nixos-borg
orivej has quit [Ping timeout: 240 seconds]
orivej has joined #nixos-borg
cransom has quit [Quit: why is weechat using 400megs of memory?]
cransom has joined #nixos-borg
MichaelRaskin has quit [Ping timeout: 276 seconds]
orivej has quit [Ping timeout: 256 seconds]
MichaelRaskin has joined #nixos-borg
<
{^_^}>
[ofborg] @Infinisil opened pull request #151 → Add infinisil to config.extra-known-users →
https://git.io/vxKzq
<
{^_^}>
→ cf556cee by @Infinisil: Add infinisil to config.extra-known-users
<
{^_^}>
→ c39c8676 by @grahamc: Merge pull request #151 from Infinisil/patch-1
<
infinisil>
Thanks!
<
gchristensen>
need to deploy it
<
infinisil>
Needs more CI!
<
gchristensen>
which is a bit delayed as I'm spinning up 3(?) more evaluators
<
gchristensen>
it fairly automatic, just delayed by the scaling up
<
infinisil>
What do you mean by spinning up 3 more evaluators? Just more of those eval checks for each PR/
<
gchristensen>
se OfBorg Evals
<
infinisil>
Ah I see
<
infinisil>
So you have like n evaluators running constantly on n cores, but now with the huge amount of PR's they can't keep up?
<
gchristensen>
yeah
<
gchristensen>
typically I run 2
<
infinisil>
Why not just spawn them everytime it needs one?
<
gchristensen>
they're individual servers
<
{^_^}>
→ 4d7338f7 by @brainrape: Add brainrape to config.extra-known-users
<
{^_^}>
→ bf9687b3 by @tadfisher: Add tadfisher to extra-known-users
<
{^_^}>
→ 8a4b1b84 by @akru: Add akru to config.extra-known-users
<
{^_^}>
→ f6172c84 by @obadz: add obadz to trusted users
<
{^_^}>
→ ab2b5c5d by @grahamc: Merge pull request #152 from obadz/patch-1
<
infinisil>
I should stop adding "just" to these questions, it makes it sound like everything is simple
<
MichaelRaskin>
Maybe evaluating architectures sequentially and and then treating evals as builds could end up helping
<
MichaelRaskin>
(But implementing that requires testing, testing requires deploying a mock setup, and that last part is scary)
<
infinisil>
Eh I bet there's lots of solutions, but if a simple one works for now there's no need to change it
<
infinisil>
"If it ain't broke, don't fix it" or something
<
MichaelRaskin>
Well, with the growing RAM requirements of eval… And with the growing architecture count…
<
infinisil>
Goddamnit, wanting to use grahacmofborg to build PR's, but both times i tried it it was an unfree package so it couldn't do it :/
jtojnar has quit [Remote host closed the connection]