gchristensen changed the topic of #nixos-dev to: NixOS Development (#nixos for questions) | https://hydra.nixos.org/jobset/nixos/trunk-combined https://channels.nix.gsc.io/graph.html | 18.09 release managers: vcunat and samueldr | https://logs.nix.samueldr.com/nixos-dev
page_ has quit [Ping timeout: 252 seconds]
page has joined #nixos-dev
orivej has joined #nixos-dev
lassulus_ has joined #nixos-dev
lassulus has quit [Ping timeout: 245 seconds]
lassulus_ is now known as lassulus
lopsided98 has quit [Quit: Disconnected]
phreedom has quit [Ping timeout: 256 seconds]
phreedom has joined #nixos-dev
lopsided98 has joined #nixos-dev
clever has quit [Ping timeout: 252 seconds]
orivej has quit [Ping timeout: 244 seconds]
clever has joined #nixos-dev
phreedom has quit [Ping timeout: 256 seconds]
phreedom has joined #nixos-dev
<niksnut> relevant to nix: https://lwn.net/Articles/754980/
<clever> that reminds me, a few years ago, when i ran nix without the sandbox, i was mounting fuse filesystems, inside nix builds!!
<clever> and nix doesnt understand how to umount them, so rm -rf just fails hard, and the tmpdir gets left behind
<clever> but i stopped doing that when i managed to break pid 1 one day, lol, and now all testing is done via qemu
<niksnut> break pid 1?
<clever> it was consuming 100% cpu and unresponsive
<clever> the machine was otherwise working, but refused to shutdown
<clever> i was playing with systemd-nspawn with a custom fuse driver for the target rootfs
sir_guy_carleton has quit [Quit: WeeChat 2.0]
WilliButz has joined #nixos-dev
goibhniu has joined #nixos-dev
<LnL> I think somebody brook evaluation of the tested job
<LnL> attribute 'diskInterface' missing, at /nix/store/5k9kk52bv6zsvsyyvpxhm8xmwyn2yjvx-source/pkgs/build-support/vm/default.nix:316:24
<srhb> f777d2b719be0db4cb7819d5b6dbdd121db29a37 perhaps
<srhb> The evaluation error is already being discussed here: https://github.com/NixOS/nixpkgs/pull/34409 -- Shall I revert it for now?
<{^_^}> #34409 (by steveeJ, 34 weeks ago, merged): qemu-vm: fix script syntax and VM args
pie___ has joined #nixos-dev
pie__ has quit [Ping timeout: 260 seconds]
pie___ has quit [Read error: Connection reset by peer]
pie___ has joined #nixos-dev
<Mic92> srhb: I guess so
<Mic92> too bad this was not catched by ofborg
<srhb> Mic92: Yeah! Oh well, things to consider for improvement. :-) Though i think evaluation of release-combined is pretty slow.
ciil has quit [Quit: Lost terminal]
ciil has joined #nixos-dev
orivej has joined #nixos-dev
<steveeJ> srhb: you pinged me. About the qemu-vm revert?
<srhb> steveeJ: Yup, just wanted to hear if you had a proper solution in the pipeline before I reverted, but I did it already. :)
<steveeJ> I read the updates on the PR. I will try to pair up with aszlig if possible and get this sorted out properly. There's a lot of redundancy that can be reduced around the qemu-vm expressions. The Perl test driver also has conditionals for checking the disk interface. Ideally we combine all of that in Mix somewhere
<steveeJ> s/Mix/Nix
<steveeJ> I don't have more than what's in the PR. I should run all nixos/tests next time ;-)
<aszlig> steveeJ: mhm, at some point i'd rewrite all that stuff into using a list in nix or maybe even an attrset (the latter would make it easier to override)
<aszlig> unfortunately qemu has some arguments that are order-dependant, so not sure whether an attrset would work
<aszlig> otoh... if we directly pass options as a qdict an attrset would work
<aszlig> actually... i'm wrong... the arglist is parsed into a qdict anyway, so it shouldn't be order dependent
<aszlig> so i'd opt for qemu -readconfig, which reads an ini-style config
<aszlig> it's then just a matter of generators.toINI
<aszlig> we could even go so far and automatically generate nixos options for *all* the qemu options
<aszlig> all the options are introspectable and have types, eg: QEMU_OPT_BOOL QEMU_OPT_BPS QEMU_OPT_IOPS QEMU_OPT_NUMBER QEMU_OPT_SIZE QEMU_OPT_STRING QEMU_OPT_THROTTLE
<niksnut> that's undesirable due to maintainability and module system bloat
<aszlig> niksnut: maintainability shouldn't be an issue, because it's just one command that directly spits out module options... module system bloat on the other hand is
<niksnut> aszlig: it tightly couples the nixos module to a particular version of qemu
<niksnut> also, somebody needs to run that command (and figure out how to do so)
<aszlig> qemu/update.sh =)
orivej has quit [Ping timeout: 252 seconds]
phreedom has quit [Ping timeout: 256 seconds]
phreedom_ has joined #nixos-dev
phreedom_ has quit [Ping timeout: 256 seconds]
phreedom has joined #nixos-dev
<gchristensen> during a remote build if the nix-build client disconnects should the remote build be canceled?
<gchristensen> right now I'm showing that didn't happen with a kernel build when my laptop crashed
orivej has joined #nixos-dev
globin has quit [Remote host closed the connection]
orivej has quit [Ping timeout: 260 seconds]
globin has joined #nixos-dev
<sphalerite> gchristensen: maybe the remote sshd is still running and hoping the connection might come back?
<gchristensen> ah maybe so
<sphalerite> as far as I've observed the builds did generally stop when the connection was lost ,although it might not happen immediately
<sphalerite> very frustrating!
<steveeJ> aszlig: no doubt that'd work much more reliably than what we currently have. it does sound a lot like rebuilding libvirt to a certain extent. has it been considered to integrate that into the tests?
globin has quit [Quit: o/]
globin has joined #nixos-dev
pie_ has joined #nixos-dev
makefu has quit [Ping timeout: 268 seconds]
pie___ has quit [Ping timeout: 252 seconds]
pie_ has quit [Read error: Connection timed out]
pie_ has joined #nixos-dev
makefu has joined #nixos-dev
orivej has joined #nixos-dev
aminechikhaoui has quit [Ping timeout: 240 seconds]
<andi-> anyone able to restart this hydra job? https://hydra.nixos.org/build/81920281 has been stuck for >2d on ike again..
makefu has quit [Ping timeout: 264 seconds]
<andi-> smae for https://hydra.nixos.org/build/81939524 but "just" 19h on sending inputs
<gchristensen> andi-: do you have a hydra account?
<andi-> gchristensen: not yet. How does that work?
<gchristensen> go to https://hydra.nixos.org/ click Sign In , then "with Google"
<andi-> ok, I did that (a few times since umatrix) but the feedback isn't really there...
<andi-> ahh there it is.. I'll pm you the account name
<gchristensen> ok you can restart jobs now andi-
<andi-> \o/
<andi-> thanks
lassulus_ has joined #nixos-dev
lassulus has quit [Ping timeout: 244 seconds]
lassulus_ is now known as lassulus
<andi-> restarting a job means cancel -> start again or is there a dedicated restart action that I haven't found yet?
<gchristensen> pretty much means that
<andi-> ok
<andi-> So that permission error on cancel is not to be expected? :D
<gchristensen> oh maybe you can't cancel :)
<gchristensen> I canceled, you can restart.
<andi-> nah
<andi-> 403
<gchristensen> hrm.
<andi-> (I tried logging out and in again..)
orivej has quit [Ping timeout: 252 seconds]
* gchristensen has no idea
aminechikhaoui has joined #nixos-dev
orivej has joined #nixos-dev
<domenkozar> anything to include into weekly tomorrow? :)
<{^_^}> nixos-weekly#64 (by domenkozar, 2 weeks ago, open): Call for Content: 2018/09
<domenkozar> gchristensen: do you think we can bump Nix on travis?
<domenkozar> copying path '/nix/store/birp3a0apx7iyl5zq71vggdizlxbrn5d-haskell-src-exts-1.20.2' from 'https://cachix.cachix.org'...
<domenkozar> error: out of memory
<domenkozar> it's getting quite annoying, I'm building with -j1 and it runs out of memory
<domenkozar> :)
<gchristensen> try it, set `nix: 2.1.2` in your yaml and see how it goes
<domenkozar> :O
<LnL> oh, that's a thing?
<gchristensen> can I take off the rest of the day and just write blog posts for WeeklY? :)
<domenkozar> approved
<gchristensen> #1 ^ you can do that
<domenkozar> moar
<gchristensen> all in one week?
<gchristensen> talking about http://gsc.io/report-crash.html would be cool
<domenkozar> copying path '/nix/store/birp3a0apx7iyl5zq71vggdizlxbrn5d-haskell-src-exts-1.20.2' from 'https://cachix.cachix.org'...
<domenkozar> std::bad_alloc
<domenkozar> copying path '/nix/store/vvl9kjp778q79ii28kfkknya6q9sgf8b-prettyprinter-ansi-terminal-1.1.1.2' from 'https://cachix.cachix.org'...
<domenkozar> wat
<domenkozar> I thought Nix 2.1 fixes that
<domenkozar> reported to
<LnL> never seen that before
<domenkozar> gchristensen: aha, 2.1.2 breaks macos since it wants to source daemon profile
<gchristensen> aye
<gchristensen> I thought it might
<domenkozar> total used free shared buffers cached
<domenkozar> Mem: 7479 1391 6088 179 170 939
<domenkozar> so nix has 6G of memory
<domenkozar> and with -j1 it runs out?
<domenkozar> and it needs to unpack 4GB for the whole substituter package
<domenkozar> something is really strange here
makefu has joined #nixos-dev
makefu has quit [Client Quit]
MichaelRaskin has joined #nixos-dev
<Mic92> domenkozar: I thought this was in an old version where it unpacked stuff to memory first.
<Mic92> ah, you already on the new one
<Mic92> I did not read this far
<Mic92> would be interesting to get a stacktrace for that, one can use gdb for that.
xeji has joined #nixos-dev
<aszlig> steveeJ: well, i think for the actual point of fixing vmWithBootLoader, we should go for a more minimal approach so it can be backported to stable
<aszlig> steveeJ: after that we can refactor that stuff seperately
<infinisil> I'd appreciate if somebody could merge #46453, I'd rather not merge my own non-trivial PR's
<{^_^}> https://github.com/NixOS/nixpkgs/pull/46453 (by Infinisil, 2 weeks ago, open): haskellPackages.shellFor: Fix ghc calls
* infinisil is off to sleep now
lopsided98 has quit [Quit: Disconnected]
lopsided98 has joined #nixos-dev
<domenkozar> Mic92: if only I could reproduce locally
xeji has quit [Quit: WeeChat 2.1]
<steveeJ> aszlig: agreed. I will take a look on the weekend if you haven't done so until then
goibhniu has quit [Ping timeout: 276 seconds]
lopsided98 has quit [Quit: Disconnected]
lopsided98 has joined #nixos-dev
<gchristensen> NixOS people -- how often are we blocked in hydra by aarch64 having a lot of builds waiting?
<samueldr> (when making my reports for 18.09, I don't often see more jobs waiting on aarch64 than x86_64-linux; darwin more often seems to be lagging behind)
<samueldr> though stable may not see the same usage