| Re: [chrony-dev] [GIT] chrony/chrony.git branch master updated. 4.1-pre1-8-g8c1e167 |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-dev Archives
]
- To: chrony-dev@xxxxxxxxxxxxxxxxxxxx
- Subject: Re: [chrony-dev] [GIT] chrony/chrony.git branch master updated. 4.1-pre1-8-g8c1e167
- From: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
- Date: Thu, 29 Apr 2021 17:09:17 +0200
- Authentication-results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=mlichvar@xxxxxxxxxx
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1619708963; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=zQ/n0vFwCk9MKvHtL715F8Zjha8tFt6Jv00dodXe4lU=; b=O0Xx1HGZbI6735Y2eZHP+hVWpjTUpzyVHHpU/k3M2FBEbsgE1avFPvcQXmb0LD0TUwpH8s elC5DR7axaIlmhCmMPDC9IEA0kOpaJvqK+ckJFvtg6JGLacL55lcb7XkwvKj3kLPHYa6rA S5pXhTlM9+x9h03T3q1oLfgYJN7WInQ=
On Thu, Apr 29, 2021 at 03:19:13PM +0200, git@xxxxxxxxxxxxx wrote:
> test: rework seccomp testing
>
> Instead of a single test with enabled seccomp, rerun all other
> non-destructive and destructive tests for each seccomp level.
It seems this greatly improved seccomp testing coverage. I already see
a second issue that it caught (getuid32 on i686 + NTS).
If you have access to a large number of different archs or Linux
systems/versions, please consider running the tests from current git.
If you see failures, you can rerun an individual test in the
test/system directory like this
TEST_SCFILTER=1 ./010-nts
Check the system (audit) log if it has the syscall number.
I'd like to release a final 4.1 in a week or two.
Thanks,
--
Miroslav Lichvar
--
To unsubscribe email chrony-dev-request@xxxxxxxxxxxxxxxxxxxx with "unsubscribe" in the subject.
For help email chrony-dev-request@xxxxxxxxxxxxxxxxxxxx with "help" in the subject.
Trouble? Email listmaster@xxxxxxxxxxxxxxxxxxxx.