nixbot

builds

succeeded container-test-run-tinc-auth-container checks.aarch64-linux.nixos-tinc-auth-container · build #327 · raw

1tribuchet: building on eliza2Machine state will be reset. To keep it, pass --keep-machine-state3start all VLans4(finished: start all VLans, in 0.00 seconds)5Initializing machine ID from random generator.6Test will time out and terminate in 3600.0 seconds7run the VM test script8start all VMs9solo: systemd-nspawn running (pid 50)10solo: Waiting for journal at /build/vm-state-solo/var/log/journal...11(finished: start all VMs, in 0.00 seconds)12solo: waiting for unit tinc.mesh.service13nixos-nspawn(solo): TAP vde-tap1 not found; container will be isolated from VDE14nixos-nspawn(solo): A common reason for this is that /dev/net is not available in the Nix sandbox. Try adding /dev/net to extra-sandbox-paths.15Note: in a future version of systemd-nspawn the default set of permitted socket address families will be restricted to AF_INET, AF_INET6 and AF_UNIX. Use --restrict-address-families= to configure the set of permitted socket address families, or set RestrictAddressFamilies= in a .nspawn file.16░ Spawning container solo on /build/vm-state-solo.17solo # [104705.026548] solo systemd-journald[58]: Journal started18solo # [104705.026600] solo systemd-journald[58]: Runtime Journal (/run/log/journal/b1ff9b0db7554044bef4f70fbc5ab48a) is 8M, max 4G, 3.9G free.19solo # [104705.031983] solo systemd[1]: Finished Apply Kernel Variables.20solo # [104705.043705] solo systemd[1]: Finished Create Static Device Nodes in /dev gracefully.21solo # [104705.068702] solo systemd[1]: Starting Flush Journal to Persistent Storage...22solo # [104705.069360] solo systemd[1]: Starting Create Static Device Nodes in /dev...23solo # [104705.080987] solo systemd-journald[58]: Time spent on flushing to /var/log/journal/b1ff9b0db7554044bef4f70fbc5ab48a is 2.369ms for 6 entries.24solo # [104705.080987] solo systemd-journald[58]: System Journal (/var/log/journal/b1ff9b0db7554044bef4f70fbc5ab48a) is 512B, max 4G, 3.9G free.25solo # [104705.089746] solo systemd[1]: Finished Create Static Device Nodes in /dev.26solo # [104705.090407] solo systemd[1]: Reached target Preparation for Local File Systems.27solo # [104705.090524] solo systemd[1]: Rule-based Manager for Device Events and Files skipped, unmet condition check ConditionPathIsReadWrite=/sys28solo # [104705.104048] solo systemd[1]: Finished Flush Journal to Persistent Storage.29solo # [104705.179896] solo systemd[1]: Finished Firewall.30solo # [104706.020815] solo systemd[1]: Mounting /run/wrappers...31solo # [104706.073604] solo systemd[1]: Mounted /run/wrappers.32solo # [104706.074492] solo systemd[1]: Reached target Local File Systems.33solo # [104706.075463] solo systemd[1]: Listening on Boot Loader Control Service Socket.34solo # [104706.076438] solo systemd[1]: Starting Create SUID/SGID Wrappers...35solo # [104706.076474] solo systemd[1]: Update Boot Loader Random Seed skipped, unmet condition check ConditionVirtualization=!container36solo # [104706.077293] solo systemd[1]: Starting Save Transient machine-id to Disk...37solo # [104706.078051] solo systemd[1]: Starting Create System Files and Directories...38solo # [104706.096507] solo systemd-tmpfiles[162]: Cannot set file attributes for '/var/empty', value=0x00000010, mask=0x00000010, ignoring: Operation not permitted39solo # [104706.096864] solo systemd-tmpfiles[162]: fchmod() of /var/log/journal failed: Operation not permitted40solo # [104706.097156] solo systemd-tmpfiles[162]: fchmod() of /var/log/journal/b1ff9b0db7554044bef4f70fbc5ab48a failed: Operation not permitted41solo # [104706.097416] solo systemd-tmpfiles[162]: fchmod() of /run/log/journal failed: Operation not permitted42solo # [104706.099578] solo suid-sgid-wrappers-start[169]: chmod: changing permissions of '/run/wrappers/wrappers.dDv0h3W1ZM/chsh': Operation not permitted43solo # [104706.100574] solo systemd[1]: suid-sgid-wrappers.service: Main process exited, code=exited, status=1/FAILURE44solo # [104706.100633] solo systemd[1]: suid-sgid-wrappers.service: Failed to read pids.max for control group /system.slice/suid-sgid-wrappers.service, ignoring: No data available45solo # [104706.100678] solo systemd[1]: suid-sgid-wrappers.service: Failed to read pids.max for control group /system.slice/suid-sgid-wrappers.service, ignoring: No data available46solo # [104706.100707] solo systemd[1]: suid-sgid-wrappers.service: Failed with result 'exit-code'.47solo # [104706.100928] solo systemd[1]: Failed to start Create SUID/SGID Wrappers.48solo # [104706.101359] solo systemd[1]: Finished Create System Files and Directories.49solo # [104706.122065] solo systemd[1]: Starting Rebuild Journal Catalog...50solo # [104706.122844] solo systemd[1]: Starting Record System Boot/Shutdown in UTMP...51solo # [104706.137334] solo systemd[1]: Finished Record System Boot/Shutdown in UTMP.52solo # [104706.160357] solo systemd[1]: etc-machine\x2did.mount: Deactivated successfully.53solo # [104706.161632] solo systemd[1]: Finished Save Transient machine-id to Disk.54solo # [104706.162786] solo systemd[1]: Finished Rebuild Journal Catalog.55solo # [104706.166869] solo systemd[1]: Starting Update is Completed...56solo # [104706.178851] solo systemd[1]: Finished Update is Completed.57solo # [104706.179036] solo systemd[1]: Reached target System Initialization.58solo # [104706.179117] solo systemd[1]: Discard unused filesystem blocks once a week skipped, unmet condition check ConditionVirtualization=!container59solo # [104706.179150] solo systemd[1]: Started Daily Cleanup of Temporary Directories.60solo # [104706.179171] solo systemd[1]: Reached target Timer Units.61solo # [104706.179293] solo systemd[1]: Listening on D-Bus System Message Bus Socket.62solo # [104706.179472] solo systemd[1]: Listening on Nix Daemon Socket.63solo # [104706.179605] solo systemd[1]: Listening on Virtual Machine and Container Registration Service Socket.64solo # [104706.179629] solo systemd[1]: Reached target Socket Units.65solo # [104706.179663] solo systemd[1]: Reached target Basic System.66solo # [104706.180997] solo systemd[1]: Starting Import lastlog data into lastlog2 database...67solo # [104706.182145] solo systemd[1]: Starting Name Service Cache Daemon (nsncd)...68solo # [104706.183011] solo systemd[1]: Starting resolvconf update...69solo # [104706.183820] solo systemd[1]: Starting Tinc Daemon - mesh...70solo # [104706.198917] solo tinc.mesh-pre-start[188]: Warning: this tinc was built without legacy protocol support; skipping RSA key generation.71solo # [104706.200941] solo systemd[1]: Started Tinc Daemon - mesh.72solo # [104706.201980] solo systemd[1]: Started tinc-auth.service.73solo # [104706.203062] solo systemd[1]: Finished Import lastlog data into lastlog2 database.74solo # [104706.210510] solo tincd[190]: [INFO tincd] tincd 0.1.0 starting, debug level 075solo # [104706.210842] solo tincd[190]: [INFO tincd] tincd starting, name=alpha76solo # [104706.210842] solo tincd[190]: [WARN tincd::keys] Warning: insecure file permissions for Ed25519 private key file `/nix/store/j2kmc5c78nif1b0bqif1pb9gzasriqwa-ed25519.priv'!77solo # [104706.210842] solo tincd[190]: [INFO tincd] Device mode: Tun, interface: dummy78solo # [104706.210842] solo tincd[190]: [INFO tincd::net] Listening on 0.0.0.0:65579solo # [104706.210842] solo tincd[190]: [INFO tincd::net] Listening on [::]:65580solo # [104706.210967] solo tincd[190]: [INFO tincd] Ready81solo # [104706.253560] solo systemd[1]: nscd.service: Failed to read pids.max for control group /system.slice/nscd.service, ignoring: No data available82solo # [104706.253598] solo systemd[1]: nscd.service: Deactivated successfully.83solo # [104706.253831] solo systemd[1]: Stopped Name Service Cache Daemon (nsncd).84solo # [104706.257857] solo systemd[1]: Starting Name Service Cache Daemon (nsncd)...85solo # [104706.263904] solo systemd[1]: Finished resolvconf update.86solo # [104706.264108] solo systemd[1]: Reached target Preparation for Network.87solo # [104706.265220] solo systemd[1]: Starting Address configuration of eth1...88solo # [104706.266210] solo systemd[1]: Starting Extra networking commands....89solo # [104706.285673] solo network-addresses-eth1-start[247]: adding address 192.168.1.1/24... done90solo # [104706.289099] solo network-addresses-eth1-start[247]: adding address 2001:db8:1::1/64... done91solo # [104706.293793] solo systemd[1]: Finished Address configuration of eth1.92solo # [104706.302351] solo tinc-auth[191]: tinc-auth: IdP listening on 127.0.0.1:844393solo # [104706.303361] solo tinc-auth[191]: tinc-auth: listening (net=mesh)94solo # [104706.335391] solo systemd[1]: Finished Extra networking commands..95solo # [104706.335542] solo systemd[1]: Reached target Network.96solo # [104706.384098] solo systemd[1]: Started Name Service Cache Daemon (nsncd).97solo # [104706.384152] solo systemd[1]: Reached target Host and Network Name Lookups.98solo # [104706.384203] solo systemd[1]: Reached target User and Group Name Lookups.99solo # [104706.384477] solo nsncd[241]: Nov 08 21:09:05.683 INFO started, config: Config { ignored_request_types: {}, worker_count: 8, handoff_timeout: 10s }, path: "/var/run/nscd/socket"100solo # [104706.385656] solo systemd[1]: Starting User Login Management...101solo # [104706.386830] solo systemd[1]: Starting Permit User Sessions...102solo # [104706.416020] solo systemd[1]: Finished Permit User Sessions.103solo # [104706.417354] solo systemd[1]: Started Console Getty.104solo # [104706.417392] solo systemd[1]: Getty on tty1 skipped, unmet condition check ConditionPathExists=/dev/tty0105solo # [104706.417414] solo systemd[1]: Reached target Login Prompts.106solo # [104707.238949] solo systemd-logind[327]: New seat seat0.107solo # [104707.240399] solo systemd[1]: Starting D-Bus System Message Bus...108solo # [104707.240700] solo systemd[1]: Started User Login Management.109solo # [104707.243779] solo systemd[1]: Starting linger-users.service...110solo # [104707.266875] solo systemd[1]: linger-users.service: Failed to read pids.max for control group /system.slice/linger-users.service, ignoring: No data available111solo # [104707.266927] solo systemd[1]: linger-users.service: Failed to read pids.max for control group /system.slice/linger-users.service, ignoring: No data available112solo # [104707.266973] solo systemd[1]: linger-users.service: Deactivated successfully.113solo # [104707.267210] solo systemd[1]: Finished linger-users.service.114solo # [104707.267448] solo systemd[1]: Reached target Multi-User System.115solo # [104707.580475] solo dbus-broker-launch[338]: Looking up NSS user entry for 'systemd-timesync'...116solo # [104707.581215] solo dbus-broker-launch[338]: NSS returned no entry for 'systemd-timesync'117solo # [104707.581215] solo dbus-broker-launch[338]: Invalid user-name in /nix/store/j162pn4f71imwb1qyzqwd6w9bzv8b65z-system-path/share/dbus-1/system.d/org.freedesktop.timesync1.conf +16: user="systemd-timesync"118solo # [104707.581888] solo systemd[1]: Started D-Bus System Message Bus.119solo # [104707.582154] solo systemd[1]: Startup finished in 2.883s.120solo # [104707.589562] solo dbus-broker-launch[338]: Ready121solo: (finished: waiting for unit tinc.mesh.service, in 3.65 seconds)122solo: waiting for unit tinc-auth.service123solo: (finished: waiting for unit tinc-auth.service, in 0.02 seconds)124solo: waiting for TCP port 8443 on localhost125Connection to localhost (127.0.0.1) 8443 port [tcp/pcsync-https] succeeded!126solo: (finished: waiting for TCP port 8443 on localhost, in 0.01 seconds)127solo: must succeed: curl -fsS http://127.0.0.1:8443/.well-known/openid-configuration128solo: (finished: must succeed: curl -fsS http://127.0.0.1:8443/.well-known/openid-configuration, in 0.02 seconds)129solo: must succeed: curl -fsS -o /dev/null -w '%{redirect_url}' 'http://127.0.0.1:8443/authorize?response_type=code&client_id=app&redirect_uri=http%3A%2F%2Fapp.example%2Fcb&state=s'130solo: (finished: must succeed: curl -fsS -o /dev/null -w '%{redirect_url}' 'http://127.0.0.1:8443/authorize?response_type=code&client_id=app&redirect_uri=http%3A%2F%2Fapp.example%2Fcb&state=s', in 0.02 seconds)131solo: must succeed: curl -fsS -X POST http://127.0.0.1:8443/token -d grant_type=authorization_code -d code=Ffbs4rqAeNVRgb48GrDroaNK7-8Hk0p0GtfUwukpjOs -d redirect_uri=http%3A%2F%2Fapp.example%2Fcb -d client_id=app -d client_secret=snakeoil132solo: (finished: must succeed: curl -fsS -X POST http://127.0.0.1:8443/token -d grant_type=authorization_code -d code=Ffbs4rqAeNVRgb48GrDroaNK7-8Hk0p0GtfUwukpjOs -d redirect_uri=http%3A%2F%2Fapp.example%2Fcb -d client_id=app -d client_secret=snakeoil, in 0.02 seconds)133solo: must succeed: curl -fsS -H 'Authorization: Bearer Hls6d_EowBVQRRAwNUSn8z95iDAKdPcvir8nVMfXewY' http://127.0.0.1:8443/userinfo134solo: (finished: must succeed: curl -fsS -H 'Authorization: Bearer Hls6d_EowBVQRRAwNUSn8z95iDAKdPcvir8nVMfXewY' http://127.0.0.1:8443/userinfo, in 0.02 seconds)135(finished: run the VM test script, in 3.75 seconds)136test script finished in 3.80s137cleanup138kill NspawnMachine (pid 50)139Container solo terminated by signal KILL.140(finished: cleanup, in 0.22 seconds)141additionally exposed symbols:142 solo,143 vlan1,144 start_all, test_script, machines, machines_qemu, machines_nspawn, vlans, driver, log, os, create_machine, subtest, run_tests, join_all, retry, serial_stdout_off, serial_stdout_on, polling_condition, BaseMachine, QemuMachine, NspawnMachine, t, debug, dump_machine_ssh