drakonis__ has quit [Remote host closed the connection]
adisbladis has quit [Quit: WeeChat 2.1]
adisbladis has joined #nixos-dev
adisbladis has quit [Quit: WeeChat 2.1]
adisbladis has joined #nixos-dev
adisbladis has quit [Quit: WeeChat 2.1]
adisbladis has joined #nixos-dev
timokau[m] has quit [Ping timeout: 240 seconds]
CrystalGamma[m] has quit [Ping timeout: 255 seconds]
thefloweringash has quit [Ping timeout: 260 seconds]
{^_^} has quit [Remote host closed the connection]
{^_^} has joined #nixos-dev
florianjacob has joined #nixos-dev
FRidh has joined #nixos-dev
<FRidh>
macs 5, 6 and 9 are idle despite a long queue
<LnL>
yeah, hydra disabled them
orivej has joined #nixos-dev
adisbladis has quit [Quit: WeeChat 2.1]
adisbladis has joined #nixos-dev
goibhniu has joined #nixos-dev
__Sander__ has joined #nixos-dev
makefu has joined #nixos-dev
makefu has quit [Quit: WeeChat 2.0]
__Sander__ has quit [Ping timeout: 272 seconds]
__Sander__ has joined #nixos-dev
makefu has joined #nixos-dev
adisbladis has quit [Quit: WeeChat 2.1]
genesis has quit [Remote host closed the connection]
genesis has joined #nixos-dev
adisbladis has joined #nixos-dev
orivej has quit [Ping timeout: 264 seconds]
phreedom has quit [Remote host closed the connection]
phreedom has joined #nixos-dev
<gchristensen>
hmm I think at least 5 should be okay
orivej has joined #nixos-dev
FRidh has quit [Quit: Konversation terminated!]
orivej has quit [Ping timeout: 272 seconds]
ben has joined #nixos-dev
ben has quit [Ping timeout: 264 seconds]
drakonis has joined #nixos-dev
orivej has joined #nixos-dev
chaker has joined #nixos-dev
<chaker>
Hola! I'm wondering what's the best way to write tests in NixOps, I don't feel like writing a single nix expression and rely on manual testing is sufficient. However the currently implemented tests aren't that obvious for me. And I feel that they're specific to tests backends than testing resources.
__Sander__ has quit [Quit: Konversation terminated!]
orivej has quit [Ping timeout: 244 seconds]
phreedom has quit [Ping timeout: 250 seconds]
phreedom_ has joined #nixos-dev
chaker has quit [Ping timeout: 272 seconds]
drakonis has quit [Remote host closed the connection]
xeji has joined #nixos-dev
drakonis_ has joined #nixos-dev
drakonis_ is now known as Drakonis
Drakonis has quit [Remote host closed the connection]
contrapumpkin has joined #nixos-dev
copumpkin has quit [Ping timeout: 240 seconds]
timokau_ has quit [Ping timeout: 268 seconds]
orivej has joined #nixos-dev
timokau_ has joined #nixos-dev
<LnL>
huh! the legacy ssh implementation uses protocol v2?
xeji has quit [Quit: WeeChat 2.1]
<samueldr>
just to be 100% sure, a 101-500 linux rebuild doesn't warrant any special treatment, right? (e.g. batching with other big changes)
<samueldr>
at 40 000 packages, 500 is small I guess
<gchristensen>
right, no special treatment
<samueldr>
the label is a scary tone of red ;)
<gchristensen>
maybe we should change the color, or dump the number-specific labels and replace it with a "Big" label
<samueldr>
at what point should I worry about the rebuild size?
<samueldr>
(I guess "when 'Big' is the label")
sphalerite has quit [Ping timeout: 264 seconds]
WilliButz has quit [Ping timeout: 268 seconds]
phreedom_ has quit [Ping timeout: 250 seconds]
phreedom has joined #nixos-dev
sphalerite has joined #nixos-dev
<gchristensen>
we have had a hard time coming up with a definition of what is too big
<Dezgeg>
I guess we could use another order of magnitude (like 500-5000 and then 5000+)
<samueldr>
I guess big also depends on the context; changing something that affects *all* of an ecosystem's package is bigger than something with more changes, but more across the board?