diff options
| author | Alois Wohlschlager <alois1@gmx-topmail.de> | 2024-05-27 17:05:44 +0200 |
|---|---|---|
| committer | Alois Wohlschlager <alois1@gmx-topmail.de> | 2024-07-25 18:21:26 +0200 |
| commit | 233408f677f8cd310d9760ff6c1bd9c14282cc57 (patch) | |
| tree | 7cc0159582904c96195fb002dd085dbc9752c5e8 /maintainers/check-syscalls.nix | |
| parent | 8d12e0fbb7306cbc58b12ef051d7067d703738de (diff) | |
libstore/build: always treat seccomp setup failures as fatal
In f047e4357b4f7ad66c2e476506bf35cab82e441e, I missed the behavior that if
building without a dedicated build user (i.e. in single-user setups), seccomp
setup failures are silently ignored. This was introduced without explanation 7
years ago (ff6becafa8efc2f7e6f2b9b889ba4adf20b8d524). Hopefully the only
use-case nowadays is causing spurious test suite successes when messing up the
seccomp filter during development. Let's try removing it.
Change-Id: Ibe51416d9c7a6dd635c2282990224861adf1ceab
Diffstat (limited to 'maintainers/check-syscalls.nix')
0 files changed, 0 insertions, 0 deletions