From: Paul Menzel <pmenzel@molgen.mpg.de>
To: Guenter Roeck <linux@roeck-us.net>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: QA: Monitor Linux log messages as port of release (candidate) testing
Date: Tue, 7 Sep 2021 15:50:39 +0200 [thread overview]
Message-ID: <38ac012a-c16e-1ba0-b386-156bb8ddecc4@molgen.mpg.de> (raw)
In-Reply-To: <20210907125354.GE4989@roeck-us.net>
Dear Guenter,
Am 07.09.21 um 14:53 schrieb Guenter Roeck:
> On Tue, Sep 07, 2021 at 10:40:31AM +0200, Paul Menzel wrote:
>> Thank you for testing release candidates and releases [1]. Is your test
>> setup documented somewhere?
>>
> Not really, except its source is available at github:
> https://github.com/groeck/linux-build-test
Thank you.
>> If not happening already, could the Linux messages (at least up to log level
>> warning) also be monitored? For example, in Linux 5.14, a new warning snuck
>> in by cefc7ca462 (ACPI: PRM: implement OperationRegion handler for the
>> PlatformRtMechanism subtype) [2], which could have been caught early on, and
>> fixed before the release.
>>
>> The test summaries would then also notify about possible behavior change.
>
> Logs are available and can be examined at kerneltests.org/builders.
Sorry for being blind. Under *qemu-tests*, looking at build #1831 [1],
clicking on *stdio* [2] under *Steps and Logfiles*, I do not see any
Linux logs.
> Reports are generated manually, so it would be way too much effort to add
> build warnings to those. Besides, logs are way too noisy to be useful in a
> summary e-mail.
Just to avoid misunderstandings, it’s about the Linux run-time logs.
> Also, Geert's build reports already provide build warnings and errors.
> The same applies to reports sent by 0-day. Indeed, I do see at least
> one 0-day report against commit cefc7ca46235.
How can I find that report?
> What would be the point of adding yet another report of build
> warnings on top of that ?
If the functionality already exists, great. But to be clear, it’s about
the runtime logs.
Kind regards,
Paul
[1]: https://kerneltests.org/builders/hwmon-x86_64-master/builds/1831
[2]:
https://kerneltests.org/builders/qemu-x86_64-master/builds/1831/steps/qemubuildcommand/logs/stdio
next prev parent reply other threads:[~2021-09-07 13:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-07 8:40 QA: Monitor Linux log messages as port of release (candidate) testing Paul Menzel
2021-09-07 12:53 ` Guenter Roeck
2021-09-07 13:50 ` Paul Menzel [this message]
2021-09-07 14:47 ` Guenter Roeck
2021-09-07 15:18 ` Paul Menzel
2021-09-07 15:28 ` Guenter Roeck
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=38ac012a-c16e-1ba0-b386-156bb8ddecc4@molgen.mpg.de \
--to=pmenzel@molgen.mpg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
/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).