From: patchwork-bot+netdevbpf@kernel.org
To: YiFei Zhu <zhuyifei@google.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
sdf@google.com, martin.lau@linux.dev, andrii@kernel.org,
songliubraving@fb.com, kurt@linutronix.de
Subject: Re: [PATCH bpf] selftests/bpf: Relax time_tai test for equal timestamps in tai_forward
Date: Wed, 13 Dec 2023 00:00:23 +0000 [thread overview]
Message-ID: <170242562384.24748.10242622405343769136.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231212182911.3784108-1-zhuyifei@google.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Tue, 12 Dec 2023 18:29:11 +0000 you wrote:
> We're observing test flakiness on an arm64 platform which might not
> have timestamps as precise as x86. The test log looks like:
>
> test_time_tai:PASS:tai_open 0 nsec
> test_time_tai:PASS:test_run 0 nsec
> test_time_tai:PASS:tai_ts1 0 nsec
> test_time_tai:PASS:tai_ts2 0 nsec
> test_time_tai:FAIL:tai_forward unexpected tai_forward: actual 1702348135471494160 <= expected 1702348135471494160
> test_time_tai:PASS:tai_gettime 0 nsec
> test_time_tai:PASS:tai_future_ts1 0 nsec
> test_time_tai:PASS:tai_future_ts2 0 nsec
> test_time_tai:PASS:tai_range_ts1 0 nsec
> test_time_tai:PASS:tai_range_ts2 0 nsec
> #199 time_tai:FAIL
>
> [...]
Here is the summary with links:
- [bpf] selftests/bpf: Relax time_tai test for equal timestamps in tai_forward
https://git.kernel.org/bpf/bpf-next/c/e1ba7f64b192
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-12-13 0:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-12 18:29 [PATCH bpf] selftests/bpf: Relax time_tai test for equal timestamps in tai_forward YiFei Zhu
2023-12-12 21:39 ` Yonghong Song
2023-12-12 21:52 ` YiFei Zhu
2023-12-13 0:01 ` Andrii Nakryiko
2023-12-19 9:57 ` Kurt Kanzenbach
2023-12-13 0:00 ` patchwork-bot+netdevbpf [this message]
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=170242562384.24748.10242622405343769136.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kurt@linutronix.de \
--cc=martin.lau@linux.dev \
--cc=sdf@google.com \
--cc=songliubraving@fb.com \
--cc=zhuyifei@google.com \
/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