diff options
| author | Dan Nicholson <dbn@endlessos.org> | 2022-01-12 17:10:56 -0700 |
|---|---|---|
| committer | Dan Nicholson <dbn@endlessos.org> | 2022-01-12 21:59:23 -0700 |
| commit | de1870df8cf6345be5f497d6a5129d5abc7398e5 (patch) | |
| tree | b630e3cc9d0da96d8f39a12377880d30c982980e /Makefile-decls.am | |
| parent | 1af0150750fbedc780e8348c5927843824c65be0 (diff) | |
| download | ostree-de1870df8cf6345be5f497d6a5129d5abc7398e5.tar.gz | |
github: Workaround glib/seccomp issue on Ubuntu impish
The ubuntu-latest VMs are currently based on 20.04 (focal). In focal,
libseccomp2 doesn't know about the close_range syscall[1], but
g_spawn_sync in impish tries to use close_range since it's defined in
glibc. That causes libseccomp2 to return EPERM as it does for any
unknown syscalls. g_spawn_sync carries on silently instead of falling
back to other means of setting CLOEXEC on open FDs. Eventually it causes
some tests to hang since once side of a pipe is never closed. Remove
this when libseccomp2 in focal is updated or glib in impish handles the
EPERM better.
1. https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1944436
Fixes: #2495
Diffstat (limited to 'Makefile-decls.am')
0 files changed, 0 insertions, 0 deletions