From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 115A4385801D; Mon, 20 Dec 2021 23:21:28 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 115A4385801D From: "evvers at ya dot ru" To: elfutils-devel@sourceware.org Subject: [Bug debuginfod/28708] run-debuginfod-webapi-concurrency.sh seems to be flaky Date: Mon, 20 Dec 2021 23:21:28 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: elfutils X-Bugzilla-Component: debuginfod X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: evvers at ya dot ru X-Bugzilla-Status: WAITING X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: elfutils-devel@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Elfutils-devel mailing list List-Unsubscribe: , List-Archive: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Dec 2021 23:21:29 -0000 https://sourceware.org/bugzilla/show_bug.cgi?id=3D28708 --- Comment #10 from Evgeny Vereshchagin --- (In reply to Mark Wielaard from comment #9) > (In reply to Evgeny Vereshchagin from comment #7) > > > Note that packit doesn't use real hardware for various architectures = but > > > "container emulation" which causes various testcases to fail. > > >=20 > > I think I ran into issues like that in > > https://github.com/evverx/elfutils/issues/32 and > > https://github.com/evverx/elfutils/issues/31. I ignore them for the most > > part. Though it would be great if they could be skipped there. Some of = them > > seem to be easy to skip because they seem to trigger seccomp filters of= some > > kind but I'm not sure about the rest. >=20 > Easiest is to run containers with --security-opt seccomp=3Dunconfined to = make > sure seccomp doesn't arbitrarily blocks syscalls (or worse returns ENOPERM > instead on ENOSYS). >=20 Those containers are launched by Packit (or, more precisely, by mock) so I can't control how they are run. According to systemd-detect --virt those are nspawn containers and I'm 50% sure those failures are caused by a bug in ei= ther systemd-nspawn or libseccomp. In the meantime, I added a couple of bash commands that show whether the te= st hit its "pid" limit set by either systemd on the host or systemd-nspawn (or both). pid.max is unfortunately set to "max" there so it isn't obvious how = many tasks can be run there at the same time. --=20 You are receiving this mail because: You are on the CC list for the bug.=