Testing with Nix - Public Room Timeline

	Testing with Nix	89 Members
		23 Servers

Load older messages

Sender	Message	Time
27 Oct 2023
l0b0	* The default is 1 GiB. Reducing to 128 MiB broke it (OOM during boot), but 256 MiB worked. So 512 MiB should be safe. Let's see if GitLab agrees… Nope 😢; testing with 256 MiB.	01:56:43
l0b0	* The default is 1 GiB. Reducing to 128 MiB broke it (OOM during boot), but 256 MiB worked. So 512 MiB should be safe. Let's see if GitLab agrees… Nope 😢; testing with 256 MiB. Also doesn't seem to be working. Maybe the problem is effectively reversed, and it's the nodes which are running low on memory, even though there is no information to that effect? Testing with 2048 MiB per node…	02:09:56
l0b0	* The default is 1 GiB. Reducing to 128 MiB broke it (OOM during boot), but 256 MiB worked (locally). So 512 MiB should be safe. Let's see if GitLab agrees… Nope 😢; testing with 256 MiB. Also doesn't seem to be working. Maybe the problem is effectively reversed, and it's the nodes which are running low on memory, even though there is no information to that effect? Testing with 2048 MiB per node…	02:14:31
l0b0	* The default is 1 GiB. Reducing to 128 MiB broke it (OOM during boot), but 256 MiB worked (locally). So 512 MiB should be safe. Let's see if GitLab agrees… Nope 😢; testing with 256 MiB. Also doesn't seem to be working. Maybe the problem is effectively reversed, and it's the nodes which are running low on memory, even though there is no information to that effect? Testing with 2048 MiB per node… Also nope 😢. WTF is going on?	02:23:22
l0b0	It looks like `nc` never returns (it has no timeout by default), meaning the 900 second timeout never triggers. Forcing a timeout with a horrible hack might work. If so, I'd like to implement https://github.com/NixOS/nixpkgs/issues/157195 to work around this more permanently.	06:01:30
l0b0	Redacted or Malformed Event	08:33:30
raitobezarius	I think you are misunderstanding that we have no guarantee Python is running inside the VM	08:34:00
l0b0	Oh right, only on the orchestrator. My bad.	08:34:38
	K900 changed their profile picture.	08:34:56
K900	How am I not in this room	08:35:05
raitobezarius	to protect you	08:35:13
l0b0	Feck. That does mean I need to keep digging into arcane shell tools to fix my tests.	08:36:07
	pbsds joined the room.	12:40:08
	Ramses 🇵🇸 joined the room.	22:53:36
29 Oct 2023
raitobezarius	Robert Hensing (roberth): do you have leftover concerns for the timeout PR or would you allow me to send it?	15:56:05
31 Oct 2023
l0b0	I'm starting to think some unreliable test runs — `waiting for the VM to finish booting` never finishing — could be caused by KVM not being set up: `Virtualisation disk image created. Could not access KVM kernel module: No such file or directory qemu-kvm: failed to initialize kvm: No such file or directory qemu-kvm: falling back to tcg`	02:43:42
l0b0	* I'm starting to think some unreliable test runs — "waiting for the VM to finish booting" never being paired up with a "(finished: waiting for the VM to finish booting, in N.M seconds)" — could be caused by KVM not being set up: `Virtualisation disk image created. Could not access KVM kernel module: No such file or directory qemu-kvm: failed to initialize kvm: No such file or directory qemu-kvm: falling back to tcg`	02:44:48
l0b0	* I'm starting to think some unreliable test runs — "waiting for the VM to finish booting" never being paired up with a "(finished: waiting for the VM to finish booting, in N.M seconds)" — could be caused by KVM not being set up: `Virtualisation disk image created. Could not access KVM kernel module: No such file or directory qemu-kvm: failed to initialize kvm: No such file or directory qemu-kvm: falling back to tcg` I don't know which level this happens at, but I'm running the `nixos/nix:2.18.1` container and setting `system-features = benchmark big-parallel kvm nixos-test`.	02:46:14
l0b0	* I'm starting to think some unreliable test runs — "waiting for the VM to finish booting" never being paired up with a "(finished: waiting for the VM to finish booting, in N.M seconds)" — could be caused by KVM not being set up: `Virtualisation disk image created. Could not access KVM kernel module: No such file or directory qemu-kvm: failed to initialize kvm: No such file or directory qemu-kvm: falling back to tcg` I don't know which level this happens at, but I'm running the `nixos/nix:2.18.1` container and setting `system-features = benchmark big-parallel kvm nixos-test`. What else do I need to do to enable KVM?	02:46:36
l0b0	* I'm starting to think some unreliable test runs — "waiting for the VM to finish booting" never being paired up with a "(finished: waiting for the VM to finish booting, in N.M seconds)" — could be caused by KVM not being set up: `Virtualisation disk image created. Could not access KVM kernel module: No such file or directory qemu-kvm: failed to initialize kvm: No such file or directory qemu-kvm: falling back to tcg` I don't know which level this happens at, but I'm running the `nixos/nix:2.18.1` container and setting `system-features = benchmark big-parallel kvm nixos-test`. What else do I need to do to enable KVM? `/dev/kvm` does not exist within the Docker image.	02:53:07
K900	Gitlab managed runners aren't guaranteed to have KVM AFAIK	07:55:16
l0b0	In reply to @k900:0upti.me Gitlab managed runners aren't guaranteed to have KVM AFAIK Oh, OK. I couldn't find a definitive answer for this anywhere, so that makes sense.	08:59:21
K900	They have it sometimes IME	08:59:30
K900	But they use multiple cloud providers for those	08:59:46
l0b0	Still, I have no idea why my tests are failing randomly, and even less how to fix it now.	08:59:46
K900	Well if there's no KVM it will fall back to software emulation	09:00:28
K900	Which is not fast	09:00:29
K900	So it'll probably just time out	09:00:39
l0b0	Oh, by the way, they don't always fail when KVM is missing.	09:00:51
l0b0	So it can't be as simple as that, either.	09:01:05

Show newer messages

Back to Room ListRoom Version: 9