[Bug debuginfod/28708] run-debuginfod-webapi-concurrency.sh seems to be flaky

["evvers at ya dot ru" <sourceware-bugzilla@sourceware.org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=28708

--- Comment #10 from Evgeny Vereshchagin <evvers at ya dot ru> ---
(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.
> > > 
> > 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.
> 
> Easiest is to run containers with --security-opt seccomp=unconfined to make
> sure seccomp doesn't arbitrarily blocks syscalls (or worse returns ENOPERM
> instead on ENOSYS).
> 

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 either
systemd-nspawn or libseccomp.

In the meantime, I added a couple of bash commands that show whether the test
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.

-- 
You are receiving this mail because:
You are on the CC list for the bug.