From: Jens Axboe <axboe@kernel.dk>
To: kernel test robot <oliver.sang@intel.com>
Cc: Ammar Faizi <ammarfaizi2@gnuweeb.org>,
lkp@lists.01.org, lkp@intel.com,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [net] 02dcea6024: INFO:task_blocked_for_more_than#seconds
Date: Sat, 30 Apr 2022 08:58:21 -0600 [thread overview]
Message-ID: <f8de18da-e6ae-e82c-c6eb-6f4de6ce8e98@kernel.dk> (raw)
In-Reply-To: <20220430144902.GB27004@xsang-OptiPlex-9020>
On 4/30/22 8:49 AM, kernel test robot wrote:
>
> (please be noted we reported
> "[net] 02dcea6024: netperf.Throughput_tps -9.1% regression"
> on https://lore.kernel.org/all/20220429062049.GA8992@xsang-OptiPlex-9020/
> yesterday, but now we found a func issue on fsmark tests.
> FYI)
Please just stop testing that branch, it's been abandoned.
--
Jens Axboe
prev parent reply other threads:[~2022-04-30 14:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-30 14:49 [net] 02dcea6024: INFO:task_blocked_for_more_than#seconds kernel test robot
2022-04-30 14:58 ` Jens Axboe [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=f8de18da-e6ae-e82c-c6eb-6f4de6ce8e98@kernel.dk \
--to=axboe@kernel.dk \
--cc=ammarfaizi2@gnuweeb.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=lkp@lists.01.org \
--cc=oliver.sang@intel.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