From: "Linux regression tracking #update (Thorsten Leemhuis)" <regressions@leemhuis.info>
To: Chris McGimpsey-Jones <chrisjones.unixmen@gmail.com>
Cc: linux-kernel@vger.kernel.org,
Linux kernel regressions list <regressions@lists.linux.dev>
Subject: Re: Latest RC causing web browser crash
Date: Wed, 22 Feb 2023 16:45:24 +0100 [thread overview]
Message-ID: <e4f69695-e444-4283-06a5-7a50d01038e0@leemhuis.info> (raw)
In-Reply-To: <e503afb9-df36-5b98-6b1b-e1ad3a9d13a7@leemhuis.info>
On 16.02.23 12:10, Linux regression tracking (Thorsten Leemhuis) wrote:
> On 30.01.23 11:11, Linux kernel regression tracking (Thorsten Leemhuis)
> wrote:
>> On 28.01.23 02:14, Chris McGimpsey-Jones wrote:
>>> Is anyone else with the latest RC having issues with Google Chrome
>>> browser, causing it to crash after a couple of minutes?
>> FWIW, this is unlikely to get any traction: nearly nobody reads the LKML
>> anymore, hence it's unlikely that someone that can help will see it.
>
> FWIW, I pointed to this problem in my weekly reports, but there was no
> reaction. That sound like this is something rare which might only happen
> on your machine.
>
> Is the problem actually still occuring?
Hmm, not reply. In that case I'm going to remove it from the tracking:
#regzbot inconclusive: reporter MIA and likely individual (local?) issue
anyway
#regzbot ignore-activity
Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
--
Everything you wanna know about Linux kernel regression tracking:
https://linux-regtracking.leemhuis.info/about/#tldr
That page also explains what to do if mails like this annoy you.
prev parent reply other threads:[~2023-02-22 15:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-28 1:14 Latest RC causing web browser crash Chris McGimpsey-Jones
2023-01-30 10:11 ` Linux kernel regression tracking (Thorsten Leemhuis)
2023-02-16 11:10 ` Linux regression tracking (Thorsten Leemhuis)
2023-02-22 15:45 ` Linux regression tracking #update (Thorsten Leemhuis) [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=e4f69695-e444-4283-06a5-7a50d01038e0@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=chrisjones.unixmen@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=regressions@lists.linux.dev \
/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).