From: Mauro Carvalho Chehab <mauro.chehab@linux.intel.com>
To: Isabella Basso <isabbasso@riseup.net>
Cc: davidgow@google.com, magalilemes00@gmail.com, maira.canal@usp.br,
dlatypov@google.com, n@nfraprado.net, brendanhiggins@google.com,
linux-kernel@vger.kernel.org, leandro.ribeiro@collabora.com,
igt-dev@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-kselftest@vger.kernel.org, tales.aparecida@gmail.com,
skhan@linuxfoundation.org, andrealmeid@riseup.net,
kunit-dev@googlegroups.com
Subject: Re: [igt-dev] [PATCH i-g-t v2 3/4] lib/igt_kmod: add compatibility for KUnit
Date: Thu, 3 Nov 2022 15:57:10 +0100 [thread overview]
Message-ID: <20221103155710.36f29dd3@maurocar-mobl2> (raw)
In-Reply-To: <20221103104840.7301df76@maurocar-mobl2>
On Thu, 3 Nov 2022 10:48:40 +0100
Mauro Carvalho Chehab <mauro.chehab@linux.intel.com> wrote:
> On Sun, 28 Aug 2022 21:09:19 -0300
> Isabella Basso <isabbasso@riseup.net> wrote:
>
> > This adds functions for both executing the tests as well as parsing (K)TAP
> > kmsg output, as per the KTAP spec [1].
> >
> > [1] https://www.kernel.org/doc/html/latest/dev-tools/ktap.html
> >
> > Signed-off-by: Isabella Basso <isabbasso@riseup.net>
>
> Hi Isabella,
>
> I'm doing some tests here with my i915 KUnit patch series.
>
> There's a problem with the way it is currently parsing the KTAP logs on
> IGT. It sounds that it is parsing the data only at the end, and not as
> they arrive. That's bad, as if something goes wrong, the previously
> reported data is still useful.
>
> Also, when there's a crash, the IGT process is getting segmentation
> fault. So, the end result is that nothing is actually reported.
>
> $ sudo ./build/tests/i915_selftest
> IGT-Version: 1.26-gbab20eb65 (x86_64) (Linux: 6.1.0-rc2-drm-990037e9984e+ x86_64)
> Segmentation fault (core dumped)
>
> However, the logs are there (see enclosed). In this specific case, there
> was a GPU hang while running one of the tests on a real hardware, which
> is something that it is actually expected at development time.
Btw, if you want to test it, the patches I'm using are at:
https://patchwork.freedesktop.org/series/110483/
The latest patch there is a workaround that fixes the issue. So, if you
apply patches 1-7 only, skipping (or reverting) patch 8, you'll be able
to reproduce the Kernel crash (which seems to be caused by the way KUnit
is initialized).
Regards,
Mauro
next prev parent reply other threads:[~2022-11-03 14:57 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-29 0:09 [igt-dev] [PATCH i-g-t v2 0/4] Add support for KUnit tests Isabella Basso
2022-08-29 0:09 ` [igt-dev] [PATCH i-g-t v2 1/4] lib/igt_kmod: rename kselftest functions to ktest Isabella Basso
2022-09-09 15:05 ` Janusz Krzysztofik
2022-08-29 0:09 ` [igt-dev] [PATCH i-g-t v2 2/4] lib/igt_kmod.c: check if module is builtin before attempting to unload it Isabella Basso
2022-08-29 7:43 ` Kamil Konieczny
2022-09-09 15:10 ` Janusz Krzysztofik
2022-08-29 0:09 ` [igt-dev] [PATCH i-g-t v2 3/4] lib/igt_kmod: add compatibility for KUnit Isabella Basso
2022-09-01 6:37 ` David Gow
2022-09-19 20:43 ` Isabella Basso
2022-09-20 0:25 ` Daniel Latypov
2022-11-01 12:43 ` Mauro Carvalho Chehab
2022-11-01 12:33 ` Mauro Carvalho Chehab
[not found] ` <F263C946-123C-407F-984D-7AC284CC1B29@riseup.net>
2022-11-01 18:03 ` Mauro Carvalho Chehab
2022-11-01 12:29 ` Mauro Carvalho Chehab
2022-09-09 15:18 ` Janusz Krzysztofik
2022-09-19 20:55 ` Isabella Basso
2022-11-03 9:48 ` Mauro Carvalho Chehab
2022-11-03 11:40 ` Mauro Carvalho Chehab
2022-11-03 14:57 ` Mauro Carvalho Chehab [this message]
2022-08-29 0:09 ` [igt-dev] [PATCH i-g-t v2 4/4] tests: DRM selftests: switch to KUnit Isabella Basso
2022-09-20 8:18 ` Petri Latvala
2022-11-01 12:54 ` Mauro Carvalho Chehab
[not found] ` <Y2EcEnAzkt1Qn341@platvala-desk.ger.corp.intel.com>
2022-11-01 13:53 ` Mauro Carvalho Chehab
2022-08-29 0:53 ` [igt-dev] ✓ Fi.CI.BAT: success for Add support for KUnit tests (rev2) Patchwork
2022-08-30 20:14 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2022-09-09 14:49 ` [igt-dev] [PATCH i-g-t v2 0/4] Add support for KUnit tests Janusz Krzysztofik
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=20221103155710.36f29dd3@maurocar-mobl2 \
--to=mauro.chehab@linux.intel.com \
--cc=andrealmeid@riseup.net \
--cc=brendanhiggins@google.com \
--cc=davidgow@google.com \
--cc=dlatypov@google.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=igt-dev@lists.freedesktop.org \
--cc=isabbasso@riseup.net \
--cc=kunit-dev@googlegroups.com \
--cc=leandro.ribeiro@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=magalilemes00@gmail.com \
--cc=maira.canal@usp.br \
--cc=n@nfraprado.net \
--cc=skhan@linuxfoundation.org \
--cc=tales.aparecida@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