From: Linus Torvalds <torvalds@linux-foundation.org>
To: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 5.14
Date: Mon, 30 Aug 2021 08:17:04 -0700 [thread overview]
Message-ID: <CAHk-=wjz+RhR8rr4rAZBPf-mxZXvn2RQe-XTQcL8X+HXBAFxBA@mail.gmail.com> (raw)
In-Reply-To: <CADVatmP8HQfZBPevLuuWtWh=1eBD=cmY84iJoMcoHh0n480Bag@mail.gmail.com>
On Mon, Aug 30, 2021 at 2:12 AM Sudip Mukherjee
<sudipm.mukherjee@gmail.com> wrote:
>
> We were recently working on openqa based testing and is a very basic
> testing for now.. Build the kernel for x86_64 and arm64, boot it on
> qemu and rpi4 and test that the desktop environment is working. And,
> it now tests mainline branch every night. So, last night it tested
> "5.14.0-7d2a07b76933" and both tests were ok.
Thanks. The more the merrier, and if you do this every night, having a
fairly low-latency "it stopped working" will be good.
Of course, if you can find some other slightly more oddball
configuration that you would also like to test, that it would be even
better.
Because while it's lovely to have more automated testing, if
_everybody_ only tests x86-64 and arm64, the less common cases get
little to no testing.
No big deal, but I thought I'd just mention it in case you go "Yeah, I
know XYZ is entirely irrelevant, but I happen to like it, so I could
easily add that to the testing too".
Linus
next prev parent reply other threads:[~2021-08-30 15:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-29 22:19 Linux 5.14 Linus Torvalds
2021-08-30 9:11 ` Sudip Mukherjee
2021-08-30 15:17 ` Linus Torvalds [this message]
2021-09-12 19:29 ` Sudip Mukherjee
2021-08-30 9:39 ` Andy Shevchenko
2021-08-30 11:28 ` Andy Shevchenko
2021-08-30 20:12 ` Guenter Roeck
2021-08-30 20:15 ` Linus Torvalds
2021-08-30 21:28 ` Peter Zijlstra
2021-08-31 11:04 ` Heiko Carstens
2021-08-30 20:32 ` Thomas Gleixner
2021-08-30 23:57 ` Thomas Gleixner
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='CAHk-=wjz+RhR8rr4rAZBPf-mxZXvn2RQe-XTQcL8X+HXBAFxBA@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sudipm.mukherjee@gmail.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).