+ Kernel Selftest
+ Anders
Hi Tim,
Thanks for your email.
On Wed, 17 Nov 2021 at 20:07, Tim Lewis <elatllat(a)gmail.com> wrote:
>
> > No regressions on arm64, arm, x86_64, and i386.
>
> I got
> proc-uptime-001: proc-uptime-001.c:39: main: Assertion `i1 >= i0' failed.
It is a known intermittent failure due to test running more than expected time
and runner script killed it.
I have noticed intermittent failures on slow devices.
You can see the history of the test case on Linux next here
intermittently failing.
I do compare between the stable-rc branches, Linux mainline and next.
https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20210924/te…
> I don't see proc-uptime-001 on
> https://github.com/Linaro/test-definitions/blob/master/automated/linux/ksel…
We will add this as known intermittent failure.
It would be great if we report this to the test author and ask them to
review the test case for
the reason for long run time on slow devices.
>
> my proc-uptime-001 history
In general when a test fails,
Please re-run the test independently for 10 times or more on the same
kernel / device before we report it as regression.
> 5.10.80-rc2-dirty:not ok 10 selftests: proc: proc-uptime-001 # exit=134
exit=134 which means Aborted.
When the test runs more than X time (45 sec i guess) the script will
be killed by the runner script.
> 5.10.80-rc1-dirty:ok 10 selftests: proc: proc-uptime-001
This test log details gives more insight that the test was timeout and Aborted.
Test output log:
--------------------
# selftests: proc: proc-uptime-001
[ 43.200262] audit: type=1701 audit(1618432600.255:6):
auid=4294967295 uid=0 gid=0 ses=4294967295 pid=11758
comm=\"proc-uptime-001\"
exe=\"/opt/kselftest_intree/proc/proc-uptime-001\" sig=6 res=1
# proc-uptime-001: proc-uptime-001.c:39: main: Assertion `i1 >= i0' failed.
# /usr/bin/tim[ 43.224097] audit: type=1701 audit(1618432600.259:7):
auid=4294967295 uid=0 gid=0 ses=4294967295 pid=11756 comm=\"timeout\"
exe=\"/usr/bin/timeout.coreutils\" sig=6 res=1
eout: the monitored command dumped core
# ./kselftest/runner.sh: line 33: 11756 Aborted
/usr/bin/timeout --foreground \"$kselftest_timeout\" \"$1\"
not ok 11 selftests: proc: proc-uptime-001 # exit=134
However, It is good to find that system running slowly.
- Naresh
Dear friend,
Here is Keith from dvd-fan, a dvd supplier for wholesale.
Just check prices comparison between dvd-fan and Amazon as below:
Godzilla vs Kong 2021: Dvd-fan 4.9USD VS Amazon 22.05USD
The Blacklist Season8: Dvd-fan 9.5USD VS Amazon 45.99USD
Illumination Presents 10-Movie Collection: Dvd-fan 15USD VS Amazon 53.
84USD
If you are interested,pls contact.
Have a good day.
Keith
Regression found on riscv and arc gcc-11 build.
Following build warnings / errors reported on linux next 20211117.
metadata:
git_describe: next-20211117
git_repo: https://gitlab.com/Linaro/lkft/mirrors/next/linux-next
git_short_log: fd96a4057bd0 (\"Add linux-next specific files for 20211117\")
target_arch: riscv
toolchain: gcc-11
build error :
--------------
In file included from net/core/dev.c:105:
include/net/gro.h: In function 'ip6_gro_compute_pseudo':
include/net/gro.h:413:22: error: implicit declaration of function
'csum_ipv6_magic'; did you mean 'csum_tcpudp_magic'?
[-Werror=implicit-function-declaration]
return ~csum_unfold(csum_ipv6_magic(&iph->saddr, &iph->daddr,
^~~~~~~~~~~~~~~
csum_tcpudp_magic
cc1: some warnings being treated as errors
Reported-by: Linux Kernel Functional Testing <lkft(a)linaro.org>
link:
https://gitlab.com/Linaro/lkft/mirrors/next/linux-next/-/jobs/1790398957#L73
build link:
-----------
https://builds.tuxbuild.com/211schgBXkq5zjdda7io29wMONF/build.log
build config:
-------------
https://builds.tuxbuild.com/211schgBXkq5zjdda7io29wMONF/config
# To install tuxmake on your system globally
# sudo pip3 install -U tuxmake
tuxmake --runtime podman --target-arch riscv --toolchain gcc-11
--kconfig defconfig
--
Linaro LKFT
https://lkft.linaro.org
Dear friend,
How are you?
Hope not disturbing you.
This is kyle, from 2ndsight medical.
We are a leading Disposable Ophthalmic surgical knife manufacturer, and
have certificated by CE (TUV) and ISO13485.
We offers sterile-packed-knife, unsterile-knife, blade tip, also OEM as
your demand.
For more information, please browsing our web: [1]www.2ndsight.cn
Good day and best regards
Kyle
Whatsapp: +86-13771700694
References
1. http://www.2ndsight.cn/