src/tests/sys/capsicum, branch stable/13FreeBSD source treehttps://cgit-dev.freebsd.org/src/atom?h=stable%2F132023-08-23T17:43:30ZRemove $FreeBSD$: one-line sh pattern2023-08-23T17:43:30ZWarner Loshimp@FreeBSD.org2023-08-22T01:32:01Zurn:sha1:023fc80ee38a117fa65b2ccb2abf8bdc7dbd6fd9
Remove /^\s*#[#!]?\s*\$FreeBSD\$.*$\n/
Similar commit in main:
(cherry picked from commit d0b2dbfa0ecf)
Remove $FreeBSD$: one-line .c pattern2023-08-23T17:43:26ZWarner Loshimp@FreeBSD.org2023-08-22T01:31:41Zurn:sha1:3d497e17ebd33fe0f58d773e35ab994d750258d6
Remove /^[\s*]*__FBSDID\("\$FreeBSD\$"\);?\s*\n/
Similar commit in main:
(cherry picked from commit 1d386b48a555)
spdx: The BSD-2-Clause-FreeBSD identifier is obsolete, drop -FreeBSD2023-07-25T15:13:49ZWarner Loshimp@FreeBSD.org2023-05-10T15:40:58Zurn:sha1:caa41f641755c935b036e17440a3b49329c904ed
The SPDX folks have obsoleted the BSD-2-Clause-FreeBSD identifier. Catch
up to that fact and revert to their recommended match of BSD-2-Clause.
Discussed with: pfg
MFC After: 3 days
Sponsored by: Netflix
(cherry picked from commit 4d846d260e2b9a3d4d0a701462568268cbfe7a5b)
Simplify the capsicum-test wrapper script2021-03-17T22:22:49ZAlex Richardsonarichardson@FreeBSD.org2021-03-02T18:27:34Zurn:sha1:cad3bfa094e6135b939a948f45c4dee2df9d64f3
Instead of running tests one-by-one with the shell wrapper we now run
the full gtest testsuite twice (once as root, once as non root). This
significantly speeds up running tests despite running them twice.
This change also passes the missing -u flag to capsicum-test that caused
test failures (https://bugs.freebsd.org/250178)
Previously, running the testsuite with the wrapper script took ~3s per
test on aarch64 QEMU, i.e. a total of almost 5 minutes.
Now it takes 6 seconds to run all tests twice.
Before:
root@freebsd-aarch64:/usr/tests/sys/capsicum # /usr/bin/time kyua test functional
94/96 passed (2 failed)
309.97 real 58.46 user 244.31 sys
After:
root@freebsd-aarch64:/usr/tests/sys/capsicum # /usr/bin/time kyua test functional
functional:test_root -> passed [2.659s]
functional:test_unprivileged -> passed [2.391s]
2/2 passed (0 failed)
5.48 real 1.06 user 2.52 sys
This overhead is caused by kyua + atf-sh spawning lots of additional
processes and can be avoided by just running the googletest test binary.
syscall seconds calls errors
fork 39.810229456 1275 0
sigprocmask 13.546928736 572 0
i.e. 1275 processes spawned to run a single test.
Test Plan: All tests pass with D28907.
PR: 250178
Reviewed By: lwhsu
Differential Revision: https://reviews.freebsd.org/D29014
(cherry picked from commit 53a535c1d80a2e5ea33a4e8807647e600402b1d8)
Update capsicum-test to git commit f4d97414d48b8f8356b971ab9f45dc5c70d53c402021-03-17T22:22:49ZAlex Richardsonarichardson@FreeBSD.org2021-03-02T16:28:26Zurn:sha1:60a9c919a53273a1535671f39084913b4eff95c5
This includes various fixes that I submitted recently such as updating the
pdkill() tests for the actual implemented behaviour
(https://github.com/google/capsicum-test/pull/53) and lots of changes to
avoid calling sleep() and replacing it with reliable synchronization
(pull requests 49,51,52,53,54). This should make the testsuite more reliable
when running on Jenkins. Additionally, process status is now retrieved using
libprocstat instead of running `ps` and parsing the output
(https://github.com/google/capsicum-test/pull/50). This fixes one previously
failing test and speeds up execution.
Overall, this update reduces the total runtime from ~60s to about 4-5 seconds.
(cherry picked from commit 955a3f9ad586f38395e66127f9f2f4afbf3d5a94)
Temporarily skip failing test cases in CI:2020-10-07T09:53:24ZLi-Wen Hsulwhsu@FreeBSD.org2020-10-07T09:53:24Zurn:sha1:2c39128febae544cdcee7c8ddae1b1e30edd4741
sys.capsicum.functional.Capability__NoBypassDAC
sys.capsicum.functional.Pdfork__OtherUserForked
PR: 250178, 250179
Sponsored by: The FreeBSD Foundation
Skip test written in Googltest in the wrapper script2020-10-07T07:23:29ZLi-Wen Hsulwhsu@FreeBSD.org2020-10-07T07:23:29Zurn:sha1:3d077160cb6852e41ba395d22baed32bc7f9c96b
This leaves the main test body untouched and only skip running in the CI env,
makes doing local test easier while developing.
PR: 244165
Sponsored by: The FreeBSD Foundation
Temporarily skip failing test cases in CI:2020-10-06T12:57:54ZLi-Wen Hsulwhsu@FreeBSD.org2020-10-06T12:57:54Zurn:sha1:c3004079793d444b5dec74989a0550de3c8e08b6
sys.capsicum.functional.ForkedOpenatTest_WithFlagInCapabilityMode___
sys.capsicum.functional.OpenatTest__WithFlag
PR: 249960
Sponsored by: The FreeBSD Foundation
Make capsicum test cases fine-grained2020-10-06T06:45:52ZLi-Wen Hsulwhsu@FreeBSD.org2020-10-06T06:45:52Zurn:sha1:194d5628721f6a306aa94f7e33be909f1ab16b49
Add a wrapping script to use ATF to run tests written with Googletest
one by one. This helps locating and tracking the failing case in CI easier.
This is a temporarily solution while Googletest support in Kyua is developing.
We will revert this once Kyua+Googletest integration is ready.
Reviewed by: emaste
Sponsored by: The FreeBSD Foundation
Differential Revision: https://reviews.freebsd.org/D25896
Do a sweep and remove most WARNS=6 settings2020-10-01T01:10:51ZKyle Evanskevans@FreeBSD.org2020-10-01T01:10:51Zurn:sha1:7cc42f6d25ef2e19059d088fa7d4853fe9afefb5
Repeating the default WARNS here makes it slightly more difficult to
experiment with default WARNS changes, e.g. if we did something absolutely
bananas and introduced a WARNS=7 and wanted to try lifting the default to
that.
Drop most of them; there is one in the blake2 kernel module, but I suspect
it should be dropped -- the default WARNS in the rest of the build doesn't
currently apply to kernel modules, and I haven't put too much thought into
whether it makes sense to make it so.