From: Jakub Kicinski <kuba@kernel.org>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: Shuah Khan <shuah@kernel.org>,
Shuah Khan <skhan@linuxfoundation.org>,
"David S. Miller" <davem@davemloft.net>,
Paolo Abeni <pabeni@redhat.com>,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
"open list:KERNEL SELFTEST FRAMEWORK
<linux-kselftest@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
lkft-triage@lists.linaro.org, Netdev" <netdev@vger.kernel.org>
Subject: Re: kselftest: net: tls: hangs
Date: Tue, 29 Mar 2022 10:56:29 -0700 [thread overview]
Message-ID: <20220329105629.731ef7d6@kernel.org> (raw)
In-Reply-To: <CA+G9fYvC3b9YwXjeAUBKbgWCgip7KioBRxH=GGNPSpyPqDy2dQ@mail.gmail.com>
On Tue, 29 Mar 2022 23:16:25 +0530 Naresh Kamboju wrote:
> > I only see build logs here, are there logs for the run?
>
> Yes. Those are only build logs.
> The test log is here but not very useful.
> https://lkft.validation.linaro.org/scheduler/job/4770773#L2700
Thanks, interesting. We have the timeout set to 30 sec so if there's no
progress for 30 sec the test should just fail. But the test setup says
no progress for 900 sec, so something must have gotten hard stuck :S
Looking forward to the update tomorrow, something to consider long term
for the test setup would be enabling CONFIG_*LOCKUP_DETECTOR and
CONFIG_DETECT_HUNG_TASK.
next prev parent reply other threads:[~2022-03-29 17:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-25 7:40 kselftest: net: tls: hangs Naresh Kamboju
2022-03-25 22:13 ` Shuah Khan
2022-03-25 23:12 ` Jakub Kicinski
2022-03-25 23:34 ` Shuah Khan
2022-03-29 14:49 ` Naresh Kamboju
[not found] ` <20220329102649.507bbf2a@kernel.org>
2022-03-29 17:46 ` Naresh Kamboju
2022-03-29 17:56 ` Jakub Kicinski [this message]
2022-03-31 7:48 ` Naresh Kamboju
2022-03-31 18:54 ` Jakub Kicinski
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=20220329105629.731ef7d6@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=linux-next@vger.kernel.org \
--cc=naresh.kamboju@linaro.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shuah@kernel.org \
--cc=skhan@linuxfoundation.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;
as well as URLs for NNTP newsgroup(s).