https://sourceware.org/bugzilla/show_bug.cgi?id=28708
--- Comment #9 from Mark Wielaard <mark at klomp dot org> --- (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). > > We do have somewhat better buildbot workers for various architectures here: > > https://builder.wildebeest.org/buildbot/#/builders?tags=elfutils > > As far as I understand the tests are run there on commits to the elfutils > repository but I'm not sure how to test "PRs" there. If it was possible to > use it before commits are merged into the master branch I wouldn't have > started using Packit on GitHub probably. There is a vacation and a nationwide lockdown coming up so I can see what I can do. I hope to connect the buildbot with patchworks so that you can easily test any submitted patch before committing. -- You are receiving this mail because: You are on the CC list for the bug.
