Re: [PATCH v1] selftests: Enhance kselftest_harness.h to print which assert failed

On 06/09/2017 03:26, Shuah Khan wrote: > On 09/05/2017 02:38 PM, Mickaël Salaün wrote: >> >> >> On 28/08/2017 18:42, Shuah Khan wrote: >>> On 08/06/2017 05:23 PM, Mickaël Salaün wrote: When a test process is not able to write to TH_LOG_STREAM, this step mechanism enable to print the ass

Re: [PATCH v1] selftests: Enhance kselftest_harness.h to print which assert failed

On 09/05/2017 02:38 PM, Mickaël Salaün wrote: > > > On 28/08/2017 18:42, Shuah Khan wrote: >> On 08/06/2017 05:23 PM, Mickaël Salaün wrote: >>> When a test process is not able to write to TH_LOG_STREAM, this step >>> mechanism enable to print the assert number which triggered the failure. >>> Thi

Re: [PATCH v1] selftests: Enhance kselftest_harness.h to print which assert failed

On 28/08/2017 18:42, Shuah Khan wrote: > On 08/06/2017 05:23 PM, Mickaël Salaün wrote: >> When a test process is not able to write to TH_LOG_STREAM, this step >> mechanism enable to print the assert number which triggered the failure. >> This can be enabled by setting _metadata->no_print to true

Re: [PATCH v1] selftests: Enhance kselftest_harness.h to print which assert failed

On 08/06/2017 05:23 PM, Mickaël Salaün wrote: > When a test process is not able to write to TH_LOG_STREAM, this step > mechanism enable to print the assert number which triggered the failure. > This can be enabled by setting _metadata->no_print to true at the > beginning of the test sequence. > >

[PATCH v1] selftests: Enhance kselftest_harness.h to print which assert failed

When a test process is not able to write to TH_LOG_STREAM, this step mechanism enable to print the assert number which triggered the failure. This can be enabled by setting _metadata->no_print to true at the beginning of the test sequence. Update the seccomp-bpf test to return 0 if a test succeede