!PbcQeaWcgMyjVfeGQN:nixos.org

Nix Mozilla 🦊🐦🐒

166 Members
A room about a number of weird animals (also known as Mozilla products): Firefox, Thunderbird, Spidermonkey, NSS, cacert. Also a little bit of fun times, small amounts of extreme, when building weird animals. But for bugs please file GitHub issues. | Release Schedule: https://whattrainisitnow.com | Crash-Stats: https://crash-stats.mozilla.org/search/?distribution_id=%3Dnixos&product=Firefox&product=Thunderbird47 Servers

Load older messages


SenderMessageTime
3 Sep 2023
@hexa:lossy.networkhexabecause this is really weird08:56:20
@hexa:lossy.networkhexawhy is it sufficient on my builders, but not on hydra's when both essentially start a naked nixos in qemu08:56:42
@vcunat:matrix.orgvcunat(I have no idea how this happens.)09:01:02
@hexa:lossy.networkhexaOK, will dig into it a bit once i can sit down09:19:00
@vcunat:matrix.orgvcunatFor now unblocked. Fixed t4b and got lucky scheduling it there on the first retry. But it will be nice if you address the fragility anyway, as restarts are needed often.11:54:57
@hexa:lossy.networkhexafor me locally the resource limit for nofile on the test script is 104857620:32:46
@hexa:lossy.networkhexaboth soft and hard20:33:48
4 Sep 2023
@nbp:mozilla.orgnbpIs this an error on the emulated system or on the host? Maybe hydra has too many concurrent jobs.09:32:39
@hexa:lossy.networkhexa
machine: must succeed: sleep 2
(finished: must succeed: sleep 2, in 2.02 seconds)
machine # base64: error while loading shared libraries: libpthread.so.0: cannot open shared object file: Error 24
machine # tail: error while loading shared libraries: libcrypto.so.3: cannot open shared object file: Error 24
machine: must succeed: stat -c '%s' /tmp/last
machine # bash: line 1: /run/current-system/sw/bin/stat: Too many open files
machine: output: 
Test "Check whether Firefox can play sound" failed with error: "command `stat -c '%s' /tmp/last` failed (exit code 126)"
cleanup
kill machine (pid 6)
machine # qemu-kvm: terminating on signal 15 from pid 4 (/nix/store/pkj7cgmz66assy7l18zc7j992npb41nx-python3-3.10.12/bin/python3.10)
(finished: cleanup, in 0.05 seconds)
kill vlan (pid 5)
13:07:44
@hexa:lossy.networkhexacould be the host, or the test runner itself13:08:24
@nbp:mozilla.orgnbp maybe lsof would help tell them apart. 13:10:25
@nbp:mozilla.orgnbpchange the test case to include the output of lsof command.13:11:06
@hexa:lossy.networkhexaa quick sampling with pustil reveals that qemu_kvm holds too many fds13:34:50
@hexa:lossy.networkhexa
vm-test-run-firefox-unwrapped> (finished: waiting for the X11 server, in 17.94 seconds)
vm-test-run-firefox-unwrapped> machine: bash=4
vm-test-run-firefox-unwrapped> machine: .nixos-test-dri=13
vm-test-run-firefox-unwrapped> machine: vde_switch=6
vm-test-run-firefox-unwrapped> machine: qemu-kvm=551
13:34:55
@hexa:lossy.networkhexa
vm-test-run-firefox-unwrapped> machine: bash=4
vm-test-run-firefox-unwrapped> machine: .nixos-test-dri=13
vm-test-run-firefox-unwrapped> machine: vde_switch=6
vm-test-run-firefox-unwrapped> machine: qemu-kvm=2006
vm-test-run-firefox-unwrapped> subtest: Check whether Firefox can play sound
13:35:07
@hexa:lossy.networkhexato me that makes it hydra's fault for constraining build jobs like that13:36:03
@k900:0upti.meK900But why would it do that on Hydra and not on other systems13:37:01
@hexa:lossy.networkhexayeah, the open question13:37:26
@hexa:lossy.networkhexa ajs124: maybe something hydra does? 13:38:01
@ajs124:ajs124.deajs124don't think that's a hydra thing. more like some strange config on the hydra build nodes.13:38:56
@hexa:lossy.networkhexayeah, trying to find that config as we speak13:39:19
@hexa:lossy.networkhexaI think we're using https://github.com/DeterminateSystems/nix-netboot-serve to serve netboot images13:40:15
@hexa:lossy.networkhexaruns on eris apparently13:40:46
@hexa:lossy.networkhexawondering if our runner configs are private?14:03:42
@hexa:lossy.networkhexaor state on eris even14:03:45
@hexa:lossy.networkhexathe nix-netboot-serve configures is too minimal14:05:49
@hexa:lossy.networkhexahttps://github.com/NixOS/equinix-metal-builders/blob/main/modules/nix.nix#L3414:22:06
@hexa:lossy.networkhexathere is a hard fdlimit on the nix-daemon14:22:18
@vcunat:matrix.orgvcunatA million (per process) sounds quite a lot.14:42:54
@vcunat:matrix.orgvcunatUnless some bad leak happens. Maybe it's more likely that it's stuck on a low soft limit or that it doesn't propagate as we'd expect.14:43:44

Show newer messages


Back to Room ListRoom Version: 9