On Sun, 29 Sept 2024 at 08:00, Pedro Orlando wrote:
>
> From: Gabriela Bittencourt
>
> Change utf8 kunit test filename and path to follow the style
> convention on Documentation/dev-tools/kunit/style.rst
>
> Co-developed-by: Pedro Orlando
> Signed-off-by: Pedro Orlando
> Co-developed-by: Danilo
On Sun, 29 Sept 2024 at 08:00, Pedro Orlando wrote:
>
> From: Gabriela Bittencourt
>
> Refactoring 'test' functions into kunit tests, to test utf-8 support in
> unicode subsystem.
>
> This allows the utf8 tests to be run alongside the KUnit test suite
> using kunit-tool, quickly compiling and run
On Tue, 24 Sept 2024 at 11:22, Luis Felipe Hernandez
wrote:
>
> This patch is a follow-up task from a discussion stemming from point 3
> in a recent patch introducing the int_pow kunit test [1] and
> documentation regarding kunit test style and nomenclature [2].
>
> Colocate all kunit test suites
Improve the error and skip condition messages to let the developer know
precisely where a test has failed. Also make better use of the ksft api
for this.
Signed-off-by: Jason A. Donenfeld
---
.../testing/selftests/vDSO/vdso_test_chacha.c | 27 ---
.../selftests/vDSO/vdso_test_getrandom.c
The chacha test can build anywhere that the vgetrandom-chacha.S file is
available, so condition it on the existence of that file, rather than a
specific arch.
There is one wrinkle, which is that x86 and x86_64 are the same ARCH,
but the code is only functional for x86_64. So filter out the test fo
Hi Shuah,
I've now read your email several times trying to figure out what you
meant and what your objections are. This series is my best attempt at
trying to satisfy that. But my understanding still has a lot of question
marks, so I may have missed your point here. Nonetheless, maybe this
moves t
Rather than building on supported archs, build on all archs, and then
use the presence of the symbol in the vDSO to either skip the test or
move forward with it.
Note that this means that this test no longer checks whether the symbol
was correctly added to the kernel. But hopefully this will be cl
kselftest/fixes build: 6 builds: 2 failed, 4 passed, 1 warning
(v6.12-rc1-9-gc66be905cda24)
Full Build Summary:
https://kernelci.org/build/kselftest/branch/fixes/kernel/v6.12-rc1-9-gc66be905cda24/
Tree: kselftest
Branch: fixes
Git Describe: v6.12-rc1-9-gc66be905cda24
Git Commit: c66be905cda24fb
Thank you!
Yiei
> On Oct 2, 2024, at 1:38 PM, Shuah Khan wrote:
>
> On 9/30/24 16:40, Yifei Liu wrote:
>> step_after_suspend_test fails with device busy error while
>> writing to /sys/power/state to start suspend. The test believes
>> it failed to enter suspend state with
>> $ sudo ./step_after_
On 9/30/24 16:40, Yifei Liu wrote:
step_after_suspend_test fails with device busy error while
writing to /sys/power/state to start suspend. The test believes
it failed to enter suspend state with
$ sudo ./step_after_suspend_test
TAP version 13
Bail out! Failed to enter Suspend state
However, in
From: Joshua Hahn
Creates a cgroup with a single nice CPU hog process running.
fork() is called to generate the nice process because un-nicing is
not possible (see man nice(3)). If fork() was not used to generate
the CPU hog, we would run the rest of the cgroup selftest suite as a
nice process.
From: Joshua Hahn
Cgroup-level CPU statistics currently include time spent on
user/system processes, but do not include niced CPU time (despite
already being tracked). This patch exposes niced CPU time to the
userspace, allowing users to get a better understanding of their
hardware limits and can
Changes in v4
- Removed unnecessary forking from selftest.
- Style changes in rstat.c (fallthrough & indents)
- Fixed a selftest bug that raised false negatives, caused by
cputime_adjust sometimes adjusting utime below ntime.
- Reworded cover letter f
Em 28/09/2024 20:58, Pedro Orlando escreveu:
From: Gabriela Bittencourt
Change utf8 kunit test filename and path to follow the style
convention on Documentation/dev-tools/kunit/style.rst
Co-developed-by: Pedro Orlando
Signed-off-by: Pedro Orlando
Co-developed-by: Danilo Pereira
Signed-off-b
[ +Alexis ]
On 9/27/24 2:05 PM, Simon Horman wrote:
If MPLS is not available in the kernel then skip MPLS tests.
This avoids the test failing in situations where the test is not
supported by the underlying kernel.
In the case where all tests are run, just skip over the MPLS tests
without alter
15 matches
Mail list logo