pbb has quit [Ping timeout: 272 seconds]
hmpffff has joined #nixos-systemd
hmpffff_ has quit [Ping timeout: 265 seconds]
andi- has quit [Ping timeout: 264 seconds]
andi- has joined #nixos-systemd
pbb has joined #nixos-systemd
pbb has quit [Quit: http://quassel-irc.org - Chat comfortably. Anywhere.]
pbb has joined #nixos-systemd
asymmetric has quit [Remote host closed the connection]
asymmetric has joined #nixos-systemd
<andi-> I think the Qt issue is a minor one. We should probably figure out why the tests never reach the multi-user target :)
<andi-> or not exactly that but why they never "finish" booting. Haven't looked into that yet and can't before the evening.. just had to kill a bunch of VMs that were stuck..
<flokli> so, I was able to run the pantheon test on my machine here
<flokli> I'll try some more tests in a bit, maybe the issue is gone, or it's also just some flakyness of some sort
<flokli> I get some warnings in there about bluez, zeitgeist and avahi not running. But that's probably expected in /that/ environment
<NinjaTrappeur> huh? Do you have a link of such a failing test?
<NinjaTrappeur> I missed that part for some reason
<NinjaTrappeur> andi- ^
<andi-> NinjaTrappeur: looking.. they do not show up as failed on hydra...
<NinjaTrappeur> ah! That's probably why I missed those.
<andi-> They'll surely occur again..
<andi-> I just looked at the running builds after I woke up and some simple VM test was stuck for >8h
<NinjaTrappeur> lesson learned: I need to build at least a test vm locally to interactively see these problems.
<andi-> The virtualbox tests are likely also just timing out
<andi-> they've been running for >1h 18min on an idle box..
<NinjaTrappeur> yes, I tried to dig a bit into that without success
<NinjaTrappeur> major rabbit hole in perspective
<andi-> I would try to focus on the smallest test that hangs and then take it from there
hmpffff_ has joined #nixos-systemd
hmpffff has quit [Ping timeout: 272 seconds]
{`-`} has joined #nixos-systemd
<flokli> plasma5 test also succeeded. I'd be tempted to say whatever issues we had with QT are not related to the systemd bump (anymore) ;-)
<NinjaTrappeur> woot
<flokli> virtualbox seems to be somewhat broken in master as well - see https://github.com/NixOS/nixpkgs/pull/82693#issuecomment-610391272
<flokli> andi-: I could get the specialisation test to run here as well
<andi-> likely.. I'll let it churn through the current state and then we can assess what is broken and needs more fixing
hmpffff has joined #nixos-systemd
hmpffff_ has quit [Ping timeout: 264 seconds]
<flokli> ok cool
<gchristensen> andi-: did you ever get that box?
<andi-> which box?
<andi-> from yesterday?
<andi-> I stopped trying after we spoke
<andi-> gchristensen: just tried again. Same (non) error :/
<gchristensen> :|
<gchristensen> I'll ping naji ...
<andi-> It isn't that bad I have enough CPUs and we are actually through the rebuilds already. Just restarted all the failed builds to be sure..
hmpffff has quit [Quit: nchrrrr…]
<ma27[m]> Does anybody want to take a look at this? https://github.com/NixOS/nixpkgs/pull/84266 :)
<{^_^}> #84266 (by Ma27, 1 week ago, open): nixos/systemd-nspawn: disallow multiple packages with `.nspawn`-units
<flokli> ma27[m]: LGTM. But, did you check upstream's issue tracker? might be overrides could also just be an upstream feature…
<{^_^}> #85334 (by flokli, 15 seconds ago, open): systemd: 243.7 -> 245
<ma27[m]> shamelessly self-requested a review :P will try to test this during the next days :)
<ma27[m]> flokli: regarding the nspawn-PR: I didn't find anything about this.... I'm actually thinking about filing a patch for this, but until then I think that my PR avoids some confusion :)
<arianvp> Networkd files also do not support overrides I think yet also use the same function for generating its config
<ma27[m]> ahh right, will update the PR accordingly, thanks! :)
<ma27[m]> arianvp: so AFAICS networkd doesn't use the `generateUnits` function, but instead creates the config files in a `listToAttrs` expr