From: jeffrin@rajagiritech.edu.in (Jeffrin Thalakkottoor)
Subject: possible BUG: selftest about raw_skew failed
Date: Sat, 21 Apr 2018 20:17:55 +0530 [thread overview]
Message-ID: <CAG=yYwmQb-zuq3V9muu=xXsRGa3s1A=fFgz-XJchCiFd+GYUYQ@mail.gmail.com> (raw)
Message-ID: <20180421144755.h8COUUOxVu009-BEpdmuepJh1OYorDGH5VAM8pZV3hg@z> (raw)
hello,
failure of a test in selftest:timers
selftests: raw_skew
========================================
WARNING: ADJ_OFFSET in progress, this will cause inaccurate results
Estimating clock drift: 17.910(est) 16.820(act) [FAILED]
Bail out!
Pass 0 Fail 0 Xfail 0 Xpass 0 Skip 0 Error 0
1..0
not ok 1..7 selftests: raw_skew [FAIL]
To reproduce :
make -C tools/testing/selftests/timers/ run_tests
Linux debian 4.17.0-rc1+ #3 SMP Sat Apr 21 03:41:44 IST 2018 x86_64 GNU/Linux
GNU Make 4.2.1
Binutils 2.30
Util-linux 2.31.1
Mount 2.31.1
Linux C Library 2.27
Dynamic linker (ldd) 2.27
readlink: missing operand
Try 'readlink --help' for more information.
Procps 3.3.14
Kbd 2.0.4
Console-tools 2.0.4
Sh-utils 8.28
Udev 238
--
software engineer
rajagiri school of engineering and technology
--
To unsubscribe from this list: send the line "unsubscribe linux-kselftest" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2018-04-21 14:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-21 14:47 jeffrin [this message]
2018-04-21 14:47 ` possible BUG: selftest about raw_skew failed Jeffrin Thalakkottoor
2018-04-26 21:28 ` tglx
2018-04-26 21:28 ` Thomas Gleixner
2018-04-27 7:41 ` mlichvar
2018-04-27 7:41 ` Miroslav Lichvar
2018-04-27 15:28 ` jeffrin
2018-04-27 15:28 ` Jeffrin Thalakkottoor
2018-04-26 21:33 ` john.stultz
2018-04-26 21:33 ` John Stultz
2018-04-27 15:27 ` jeffrin
2018-04-27 15:27 ` Jeffrin Thalakkottoor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAG=yYwmQb-zuq3V9muu=xXsRGa3s1A=fFgz-XJchCiFd+GYUYQ@mail.gmail.com' \
--to=jeffrin@rajagiritech.edu.in \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).