![]() Started Update UTMP about System Runlevel Changes. =30= Using Valgrind-3.14.0 and LibVEX rerun with -h for copyright info =30= Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. rvice: Changed start -> Valgrind confirms that: rvice: Main process exited, code=dumped, status=6/ABRT Received SIGCHLD from PID 30 (test-jobs.sh).Ĭhild 30 (test-jobs.sh) died (code=dumped, status=6/ABRT) rvice: Got notification message from PID 17 (FDSTORE=1) rvice: Kernel keyring access prohibited, ignoring. Starting [0 1 39mSleep for 1 minute[0m. rvice: Failed to set 'pids.max' attribute on '/system.slice/rvice' to '737': No such file or directory rvice: Failed to reset devices.allow/ny: No such file or directory rvice: Failed to set 'memory.limit_in_bytes' attribute on '/system.slice/rvice' to '-1': No such file or directory Hello-after-sleep.target: Enqueued job hello-after-sleep.target/start as 126 rvice: Installed new job rvice/start as 127 Hello-after-sleep.target: Installed new job hello-after-sleep.target/start as 126 rvice: Installed new job rvice/start as 175 Keeping job rvice/start because of hello-after-sleep.target/start Relevant part of the logs: rvice: Failed to set 'memory.limit_in_bytes' attribute on '/system.slice/rvice' to '-1': No such file or directory To get as much information as possible I ran the offending job with debug logging and kept all the test artifacts: rvice: Received EPOLLHUP on stored fd 34 (stored), closing. Sent message type=signal sender=n/a destination=n/a path=/org/freedesktop/systemd1/unit/systemd_2dupdate_2dutmp_2drunlevel_2eservice interface= member=PropertiesChanged cookie=29 reply_cookie=0 signature=saas error-name=n/a error-message=n/a Started [0 1 39mUpdate UTMP about System Runlevel Changes[0m.īus private-bus-connection: changing state RUNNING → CLOSING rvice: Job 66 rvice/start finished, result=done rvice: Main process exited, code=exited, status=0/SUCCESS Also, it happens only under systemd-nspawn (to be more precise: under systemd-nspawn in a KVM). I failed to reproduce it locally (even though I used the exact same script as the CI itself), and I'm still not sure if it's not just a misconfiguration on my side or a real issue. I recently started playing with upstream systemd on openSUSE Tumbleweed in and stumbled across an issue which affects several tests. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |