From: Rachel Sibley <rasibley@redhat.com>
To: Greg KH <gregkh@linuxfoundation.org>,
Deepa Dinamani <deepa.kernel@gmail.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
Naresh Kamboju <naresh.kamboju@linaro.org>,
Linux Stable maillist <stable@vger.kernel.org>,
Eryu Guan <guaneryu@gmail.com>,
lkft-triage@lists.linaro.org,
CKI Project <cki-project@redhat.com>
Subject: Re: ❌ FAIL: Test report for kernel 5.3.8-rc2-96dab43.cki (stable)
Date: Tue, 29 Oct 2019 16:08:27 -0400 [thread overview]
Message-ID: <114dc6b2-846b-240d-db33-dd67aac51d30@redhat.com> (raw)
In-Reply-To: <20191029181223.GB587491@kroah.com>
On 10/29/19 2:12 PM, Greg KH wrote:
> On Tue, Oct 29, 2019 at 07:57:05AM -0700, Deepa Dinamani wrote:
>> The test is expected to fail on all kernels without the series.
>>
>> The series is a bugfix in the sense that vfs is no longer allowed to
>> set timestamps that filesystems have no way of supporting.
>> There have been a couple of fixes after the series also.
>>
>> We can either disable the test or include the series for stable kernels.
> I don't see adding this series for the stable kernels, it does not make
> sense.
I'm not sure what the final decision is here, but I've moved the test to
a waived status for now,
which means it should stop causing the job to fail. However, you may see
a few lingering
reports sneak in before I made this change. Once resolved, I'll remove
the waived tag.
Thanks,
Rachel
> thanks,
>
> greg k-h
>
next prev parent reply other threads:[~2019-10-29 20:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-29 2:03 ❌ FAIL: Test report for kernel 5.3.8-rc2-96dab43.cki (stable) CKI Project
2019-10-29 5:25 ` Naresh Kamboju
2019-10-29 7:33 ` Murphy Zhou
2019-10-29 8:08 ` Greg KH
2019-10-29 9:11 ` Murphy Zhou
2019-10-29 9:21 ` Greg KH
2019-10-29 11:31 ` Sasha Levin
2019-10-29 12:40 ` Murphy Zhou
2019-10-29 14:57 ` Deepa Dinamani
2019-10-29 18:12 ` Greg KH
2019-10-29 20:08 ` Rachel Sibley [this message]
2019-10-29 21:21 ` Deepa Dinamani
2019-10-29 21:55 ` Rachel Sibley
2019-10-30 2:38 ` Murphy Zhou
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=114dc6b2-846b-240d-db33-dd67aac51d30@redhat.com \
--to=rasibley@redhat.com \
--cc=arnd@arndb.de \
--cc=cki-project@redhat.com \
--cc=deepa.kernel@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=guaneryu@gmail.com \
--cc=lkft-triage@lists.linaro.org \
--cc=naresh.kamboju@linaro.org \
--cc=stable@vger.kernel.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