From: Naresh Kamboju <naresh.kamboju@linaro.org>
To: LTP List <ltp@lists.linux.it>,
open list <linux-kernel@vger.kernel.org>,
linux-fsdevel@vger.kernel.org, regressions@lists.linux.dev,
lkft-triage@lists.linaro.org
Cc: Andrew Morton <akpm@linux-foundation.org>,
David Hildenbrand <david@redhat.com>,
Kees Cook <keescook@chromium.org>,
Alexey Dobriyan <adobriyan@gmail.com>,
Luis Chamberlain <mcgrof@kernel.org>,
Muchun Song <songmuchun@bytedance.com>,
Peter Xu <peterx@redhat.com>,
Stephen Rothwell <sfr@canb.auug.org.au>
Subject: [next] LTP: readahead02.c:295: TFAIL: readahead failed to save any I/O
Date: Thu, 24 Feb 2022 14:57:59 +0530 [thread overview]
Message-ID: <CA+G9fYs_8ww=Mi4o4XXjQxL2XJiTiAUbMd1WF08zL+FoiA7GRw@mail.gmail.com> (raw)
On Linux next 20220222 tag LTP syscalls test case readahead02 failed.
Please find detail test output on below link [1]
test failed log:
--------------------
readahead02.c:181: TPASS: offset is still at 0 as expected
readahead02.c:285: TINFO: read_testfile(0) took: 37567 usec
readahead02.c:286: TINFO: read_testfile(1) took: 37263 usec
readahead02.c:288: TINFO: read_testfile(0) read: 0 bytes
readahead02.c:290: TINFO: read_testfile(1) read: 0 bytes
readahead02.c:295: TFAIL: readahead failed to save any I/O
Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
--
Linaro LKFT
https://lkft.linaro.org
[1] https://lkft.validation.linaro.org/scheduler/job/4607403#L16941
next reply other threads:[~2022-02-24 9:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-24 9:27 Naresh Kamboju [this message]
2022-02-24 19:40 ` [next] LTP: readahead02.c:295: TFAIL: readahead failed to save any I/O Matthew Wilcox
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='CA+G9fYs_8ww=Mi4o4XXjQxL2XJiTiAUbMd1WF08zL+FoiA7GRw@mail.gmail.com' \
--to=naresh.kamboju@linaro.org \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=keescook@chromium.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=ltp@lists.linux.it \
--cc=mcgrof@kernel.org \
--cc=peterx@redhat.com \
--cc=regressions@lists.linux.dev \
--cc=sfr@canb.auug.org.au \
--cc=songmuchun@bytedance.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;
as well as URLs for NNTP newsgroup(s).