<
Enzime>
if Hydra kept track of build times, you could estimate a rebuild time for the packages
<
Enzime>
then tagging could be based on time as opposed to purely amount of packages
<
Enzime>
as that makes no indication toward their weight/complexity
goibhniu has quit [Ping timeout: 268 seconds]
_rvl has quit [Ping timeout: 260 seconds]
_rvl has joined #nixos-dev
<
niksnut>
Hydra does keep track of build times, but it's not necessarily easy to put that info to good use
<
clever>
and it doesnt toposort the queue, so it may build derivation A under B, because B depended on A
<
clever>
and then the logs for the A job dont say anything
<
niksnut>
I think that can only happen if the build with derivation A at top-level hasn't been loaded from the queue yet
globin has quit [Ping timeout: 265 seconds]
jtojnar has quit [Ping timeout: 264 seconds]
<
clever>
in the example above, the same job, within a different jobset (a pr build) had built it already, so a toposort wouldnt have actually helped
lassulus_ has joined #nixos-dev
jtojnar has joined #nixos-dev
lassulus has quit [Ping timeout: 252 seconds]
lassulus_ is now known as lassulus
drakonis_ has joined #nixos-dev
lassulus has quit [Ping timeout: 244 seconds]
lassulus has joined #nixos-dev
orivej has quit [Ping timeout: 252 seconds]
orivej has joined #nixos-dev
lassulus has quit [Ping timeout: 244 seconds]
orivej has quit [Ping timeout: 272 seconds]
lassulus has joined #nixos-dev
orivej has joined #nixos-dev
noefk has joined #nixos-dev
drakonis_ has quit [Remote host closed the connection]
phreedom_ has joined #nixos-dev
phreedom has quit [Remote host closed the connection]
orivej has quit [Ping timeout: 252 seconds]
Cale has quit [Remote host closed the connection]
orivej has joined #nixos-dev
goibhniu has joined #nixos-dev
orivej has quit [Ping timeout: 244 seconds]
__Sander__ has joined #nixos-dev
__Sander__ has quit [Ping timeout: 272 seconds]
__Sander__ has joined #nixos-dev
goibhniu has quit [Ping timeout: 244 seconds]
goibhniu has joined #nixos-dev
<
manveru>
when was the deadline for 18.09?
<
manveru>
should probably make 2.5 the default ruby for it
fadenb has quit [Quit: irc_error]
fadenb has joined #nixos-dev
orivej has joined #nixos-dev
orivej has quit [Ping timeout: 276 seconds]
orivej has joined #nixos-dev
WilliButz has joined #nixos-dev
drakonis_ has joined #nixos-dev
<
samueldr>
manveru: what's left?
<
samueldr>
or, what needs to be done?
orivej has quit [Ping timeout: 272 seconds]
<
manveru>
samueldr: just running nix-review
<
manveru>
not sure what might break, but it should in theory be fine :)
<
samueldr>
wrt 2.6; with annual ruby releases, on december 25th, the next release will always be around the corner for xx.09 :)
<
manveru>
but that's alright for 19.03 then
<
manveru>
there's no rvm patchset for 2.6 yet anyway
<
manveru>
i thought about packaging the preview-2 branch... would be nice to have those in nixpkgs too
<
manveru>
but the way it's coupled with railsexpress atm makes it hard
globin has joined #nixos-dev
<
gchristensen>
I just had a nix derivation realize in to the totally wrong thing
<
gchristensen>
many times, actually
<
gchristensen>
niksnut: can you take a look? very mysterious, seems very bad that pkgs.writeScript can fail-and-succeed
<
gchristensen>
maybe you have ideas on data I can provide
<
gchristensen>
man, I had hundreds of derivation builds become empty
<
LnL>
is this only with check mode?
<
gchristensen>
no, nix-build produced them the first time empty and --check is showing the second time, it is creating them properly
<
clever>
gchristensen: can you nix-build with -vvvv ?
<
LnL>
could you make a fully reproducible expression
<
gchristensen>
that is a problem, I can't
<
gchristensen>
when I build them again, they are properly created.
<
cransom>
have a transient failure with a disk full or something silly like that?
<
gchristensen>
brand new machine, several tb free
<
manveru>
ok, nix-review just ate all my harddisk
<
niksnut>
gchristensen: did you have a system crash or something?
<
niksnut>
and what does nix-store --verify-path say?
<
gchristensen>
no, nothing crashed and dmesg doesn't say anything
<
gchristensen>
:/ seems I cant verify the path anymore... I thought I left a few to work with but accidentally fixed them all
<
Dezgeg>
IIRC domenkozar had reported something similar in the past (unresolved)
lassulus has quit [Ping timeout: 244 seconds]
<
gchristensen>
cransom: check your PMs :)
lassulus has joined #nixos-dev
__Sander__ has quit [Quit: Konversation terminated!]
orivej has joined #nixos-dev
orivej has quit [Ping timeout: 245 seconds]
orivej has joined #nixos-dev
orivej has quit [Ping timeout: 268 seconds]
drakonis_ has quit [Remote host closed the connection]
pie_ has joined #nixos-dev
orivej has joined #nixos-dev
Drakonis has joined #nixos-dev
tilpner has quit [Remote host closed the connection]
tilpner has joined #nixos-dev
<
infinisil>
gchristensen: Neat!
Drakonis has quit [Remote host closed the connection]
coconnor has quit [Quit: leaving]
<
{^_^}>
nixos-weekly#63 (by domenkozar, 6 days ago, open): Call for Content: 2018/08
goibhniu has quit [Ping timeout: 244 seconds]
<
infinisil>
domenkozar: There doesn't seem to be all that much content every week, have you thought about making it a monthly thing instead?
<
aszlig>
domenkozar: hm, just added a PR for nix to use 64bit integers... it's a very very small thing, but if you get nothing else, maybe include it?
<
{^_^}>
nix#2378 (by aszlig, 12 minutes ago, open): libexpr: Use int64_t for NixInt
<
aszlig>
domenkozar: also thanks for doing the weekly news :-)
<
aszlig>
domenkozar++
<
{^_^}>
domenkozar's karma got increased to 2
ivan has joined #nixos-dev
<
{^_^}>
nix#2336 (by ivan, 3 weeks ago, open): repl: don't add trailing spaces to history lines
Lisanna has joined #nixos-dev