<jcrben>
teto1: noticed your comment about the testsuite at https://github.com/NixOS/nix/issues/2209#issuecomment-394988952 and I see you have a note to self from irc - which piques my curiosity - where are the build logs for nix? seems like they could be linked out more prominently (if not listed with a github badge)
<samueldr>
LnL: anecdotally, ripping the network interface (usb thankfully) seems to not kill the build
<samueldr>
with that, I mean intentionally not plugging it back in either
<manveru>
matthewbauer: start it in a tmux
<Dezgeg>
shouldn't help
<matthewbauer>
well i'm not on the machine directly at all - nix is managing the connection
<manveru>
ah, i misunderstood
<LnL>
samueldr: well, pretty sure it's not supposed to do that
<manveru>
you build locally but with distributed builds?
<Dezgeg>
probably it depends on luck, like whether or not the log spam output is too much to fill any buffers
<samueldr>
unless it was a happy coincidence and the built finished before the connection closed
<matthewbauer>
maybe setting TCPKeepAlive would work?
<matthewbauer>
or sorry disabling TCPKeepAlive
<LnL>
possibly
<matthewbauer>
i guess that's server side though
<LnL>
from what I understand the build is supposed to die when the nix-store --serve --write process exits on the build host
<matthewbauer>
yeah - i want it to *just* work out of the box with Nix. once the build is started the remote should have more than enough information to finish
<LnL>
that would mean canceling nix-build won't do anything
<LnL>
and the next build will wait for possibly hours for the previous build to finish with no way to cancel it
<matthewbauer>
yes maybe it could be an option passed to nix? like --nohup or something
<gchristensen>
what is the root problem you're trying to solve? what happened to spur this?
<matthewbauer>
well i had a mass rebuild yesterday & i took my laptop home while it was running. since the actual build was running on another machine i thought it would keep running - it did for a little bit but then got an "unexpected end-of-file" message
<gchristensen>
that is disappointing
<matthewbauer>
yeah it's something that happens frequently for different reasons on a laptop. desktop people might not run into this (although things like network failure could also happen)
ixxie has joined #nixos-dev
ixxie has quit [Ping timeout: 268 seconds]
<LnL>
oh
<LnL>
is there any reason not to backport nix 2.0.4 to 18.03?
<gchristensen>
should be safe?
<LnL>
just noticed it's still on 2.0.2
<gchristensen>
should be fine
<LnL>
pushed :)
Sonarpulse has joined #nixos-dev
orivej has quit [Ping timeout: 276 seconds]
matthewbauer has quit [Read error: Connection reset by peer]
matthewbauer has joined #nixos-dev
Sonarpulse has quit [Ping timeout: 276 seconds]
Sonarpulse has joined #nixos-dev
MichaelRaskin has joined #nixos-dev
matthewbauer has quit [Remote host closed the connection]
orivej has joined #nixos-dev
matthewbauer has joined #nixos-dev
pie_ has quit [Ping timeout: 264 seconds]
matthewbauer has quit [Remote host closed the connection]
matthewbauer has joined #nixos-dev
matthewbauer has quit [Remote host closed the connection]
<Profpatsch>
peti: haskellPackages.hnix is currently broken:
<Profpatsch>
Setup: ./hnix.cabal:588: 'else' branch of 'if' is empty