linux-kselftest.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: john.stultz@linaro.org (John Stultz)
Subject: possible BUG: selftest about raw_skew failed
Date: Thu, 26 Apr 2018 14:33:11 -0700	[thread overview]
Message-ID: <CALAqxLWphJvPe=v2T2ksjHnQP1Vu7+gZernEgFVXcx5kB+efsQ@mail.gmail.com> (raw)
Message-ID: <20180426213311.u1qQgsKN3B5vYPCIuwga7riWMa4ARU9SZnOT6oPwQ0s@z> (raw)
In-Reply-To: <CAG=yYwmQb-zuq3V9muu=xXsRGa3s1A=fFgz-XJchCiFd+GYUYQ@mail.gmail.com>

On Sat, Apr 21, 2018 at 7:47 AM, Jeffrin Thalakkottoor
<jeffrin@rajagiritech.edu.in> wrote:
> 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]

So you're ignoring the warning above. If an ADJ_OFFSET operation is
going on, ntpd (or something similar) is changing the clock, which
will kill the estimated drift calculation.

-john
--
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

  parent reply	other threads:[~2018-04-26 21:33 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-21 14:47 possible BUG: selftest about raw_skew failed jeffrin
2018-04-21 14:47 ` 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 [this message]
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='CALAqxLWphJvPe=v2T2ksjHnQP1Vu7+gZernEgFVXcx5kB+efsQ@mail.gmail.com' \
    --to=john.stultz@linaro.org \
    /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).