From: Stephen Boyd <sboyd@kernel.org>
To: Nico Pache <npache@redhat.com>
Cc: KUnit Development <kunit-dev@googlegroups.com>,
linux-clk@vger.kernel.org, Shuah Khan <skhan@linuxfoundation.org>,
Audra Mitchell <aubaker@redhat.com>,
Donald Zickus <dzickus@redhat.com>
Subject: Re: [Bug Report] Multiple S390x KUNIT clk failures
Date: Tue, 14 May 2024 15:04:12 -0700 [thread overview]
Message-ID: <9be47cd74b62ba8e4a36f3139fc8d275.sboyd@kernel.org> (raw)
In-Reply-To: <CAA1CXcALWqxfoWsv_wuiu-hAmX=AosvEedheGJUQHAhDCZf2Sg@mail.gmail.com>
Quoting Nico Pache (2024-05-14 00:14:24)
> Hi Stephen,
>
> Yes, we have that commit. This is failing on fedora-ark, so it's
> constantly updated to match upstream, and the earliest recorded
> instance of it failing in our environment is v6.1.
>
Please don't top post. I'm unable to run s390 kunit tests in qemu. They
seem to crash before finishing.
./tools/testing/kunit/kunit.py run --kunitconfig=lib/kunit --arch=s390 --cross_compile=/path/to/s390-linux-
[14:55:10] Starting KUnit Kernel (1/1)...
[14:55:10] ============================================================
Running tests with:
$ qemu-system-s390x -nodefaults -m 1024 -kernel .kunit/arch/s390/boot/bzImage -append 'kunit.enable=1 console=ttyS0 kunit_shutdown=reboot' -no-reboot -nographic -serial stdio -machine s390-ccw-virtio -cpu qemu
[14:55:11] ============================= =============================
[14:55:11] ================= example_init (1 subtest) =================
[14:55:11] [PASSED] example_init_test
[14:55:11] ================== [PASSED] example_init ===================
[14:55:11] ============================= =============================
[14:55:11] ============= kunit_executor_test (8 subtests) =============
[14:55:11] [PASSED] parse_filter_test
[14:55:11] [PASSED] filter_suites_test
[14:55:11] [PASSED] filter_suites_test_glob_test
[14:55:11] [PASSED] filter_suites_to_empty_test
[14:55:11] [PASSED] parse_filter_attr_test
[14:55:11] [PASSED] filter_attr_test
[14:55:11] [PASSED] filter_attr_empty_test
[14:55:11] [PASSED] filter_attr_skip_test
[14:55:11] [ERROR] Test: kunit_executor_test: Expected test number 1 but found 2
[14:55:11] =============== [PASSED] kunit_executor_test ===============
[14:55:11] ============================= =============================
[14:55:11] ============ kunit-try-catch-test (2 subtests) =============
[14:55:11] [PASSED] kunit_test_try_catch_successful_try_no_catch
[14:55:11] [PASSED] kunit_test_try_catch_unsuccessful_try_does_catch
[14:55:11] [ERROR] Test: kunit-try-catch-test: Expected test number 1 but found 3
[14:55:11] ============== [PASSED] kunit-try-catch-test ===============
[14:55:11] ============================= =============================
[14:55:11] ============ kunit-resource-test (12 subtests) =============
[14:55:11] [PASSED] kunit_resource_test_init_resources
[14:55:11] [PASSED] kunit_resource_test_alloc_resource
[14:55:11] [PASSED] kunit_resource_test_destroy_resource
[14:55:11] [PASSED] kunit_resource_test_remove_resource
[14:55:11] [PASSED] kunit_resource_test_cleanup_resources
[14:55:11] [PASSED] kunit_resource_test_proper_free_ordering
[14:55:11] [PASSED] kunit_resource_test_static
[14:55:11] [PASSED] kunit_resource_test_named
[14:55:11] [PASSED] kunit_resource_test_action
[14:55:11] [PASSED] kunit_resource_test_remove_action
[14:55:11] [PASSED] kunit_resource_test_release_action
[14:55:11] [PASSED] kunit_resource_test_action_ordering
[14:55:11] [ERROR] Test: kunit-resource-test: Expected test number 1 but found 4
[14:55:11] =============== [PASSED] kunit-resource-test ===============
[14:55:11] ============================= =============================
[14:55:11] =============== kunit-log-test (2 subtests) ================
[14:55:11] [PASSED] kunit_log_test
[14:55:11] [SKIPPED] kunit_log_newline_test
[14:55:11] [ERROR] Test: kunit-log-test: Expected test number 1 but found 5
[14:55:11] ================= [PASSED] kunit-log-test ==================
[14:55:11] ============================= =============================
[14:55:11] ================ kunit_status (2 subtests) =================
[14:55:11] [PASSED] kunit_status_set_failure_test
[14:55:11] [PASSED] kunit_status_mark_skipped_test
[14:55:11] [ERROR] Test: kunit_status: Expected test number 1 but found 6
[14:55:11] ================== [PASSED] kunit_status ===================
[14:55:11] ============================= =============================
[14:55:11] ================ kunit_current (2 subtests) ================
[14:55:11] [PASSED] kunit_current_test
[14:55:11] [PASSED] kunit_current_fail_test
[14:55:11] [ERROR] Test: kunit_current: Expected test number 1 but found 7
[14:55:11] ================== [PASSED] kunit_current ==================
[14:55:11] ============================= =============================
[14:55:11] ================ kunit_device (3 subtests) =================
[14:55:11] [PASSED] kunit_device_test
[14:55:11] [PASSED] kunit_device_cleanup_test
[14:55:11] [PASSED] kunit_device_driver_test
[14:55:11] [ERROR] Test: kunit_device: Expected test number 1 but found 8
[14:55:11] ================== [PASSED] kunit_device ===================
[14:55:11] ============================= =============================
[14:55:11] ============= string-stream-test (12 subtests) =============
[14:55:11] [PASSED] string_stream_managed_init_test
[14:55:11] [PASSED] string_stream_unmanaged_init_test
[14:55:11] [PASSED] string_stream_managed_free_test
[14:55:11] [PASSED] string_stream_resource_free_test
[14:55:11] [PASSED] string_stream_line_add_test
[14:55:11] [PASSED] string_stream_variable_length_line_test
[14:55:11] [PASSED] string_stream_append_test
[14:55:11] [PASSED] string_stream_append_auto_newline_test
[14:55:11] [PASSED] string_stream_append_empty_string_test
[14:55:11] [PASSED] string_stream_no_auto_newline_test
[14:55:11] [PASSED] string_stream_auto_newline_test
[14:55:11] [PASSED] string_stream_performance_test
[14:55:11] [ERROR] Test: string-stream-test: Expected test number 1 but found 9
[14:55:11] =============== [PASSED] string-stream-test ================
[14:55:11] ============================= =============================
[14:55:11] =================== example (9 subtests) ===================
[14:55:11] [PASSED] example_simple_test
[14:55:11] [SKIPPED] example_skip_test
[14:55:11] [ERROR] Test: example: missing expected subtest!
[14:55:11]
[14:55:11] # example_mark_skipped_test: initializing
[14:55:11]
[14:55:11] # example_mark_skipped_test: You should see a line below.
[14:55:11] [CRASHED]
[14:55:11] [ERROR] Test: example: missing expected subtest!
[14:55:11] [CRASHED]
[14:55:11] [ERROR] Test: example: missing expected subtest!
[14:55:11] [CRASHED]
[14:55:11] [ERROR] Test: example: missing expected subtest!
[14:55:11] [CRASHED]
[14:55:11] [ERROR] Test: example: missing expected subtest!
[14:55:11] [CRASHED]
[14:55:11] [ERROR] Test: example: missing expected subtest!
[14:55:11] [CRASHED]
[14:55:11] [ERROR] Test: example: missing expected subtest!
[14:55:11] [CRASHED]
[14:55:11] [ERROR] Test: example: missing subtest result line!
[14:55:11]
[14:55:11] # module: kunit_example_test
[14:55:11] ==================== [CRASHED] example =====================
[14:55:11]
[14:55:11] # example: initializing suite
[14:55:11]
[14:55:11] ======================== [CRASHED] ========================
[14:55:11]
[14:55:11] ======================== [CRASHED] ========================
[14:55:11]
[14:55:11] ======================== [CRASHED] ========================
[14:55:11]
[14:55:11] ======================== [CRASHED] ========================
[14:55:11]
[14:55:11] ======================== [CRASHED] ========================
[14:55:11]
[14:55:11] ======================== [CRASHED] ========================
[14:55:11]
[14:55:11] ======================== [CRASHED] ========================
[14:55:11]
[14:55:11] ======================== [CRASHED] ========================
[14:55:11]
[14:55:11] ======================== [CRASHED] ========================
[14:55:11]
[14:55:11] ======================== [CRASHED] ========================
[14:55:11] [ERROR] Test: main: missing expected subtest!
[14:55:11] [CRASHED]
[14:55:11] [ERROR] Test: main: missing expected subtest!
[14:55:11] [CRASHED]
[14:55:11] [ERROR] Test: main: missing expected subtest!
[14:55:11] [CRASHED]
[14:55:11] [ERROR] Test: main: missing expected subtest!
[14:55:11] [CRASHED]
[14:55:11] [ERROR] Test: main: missing expected subtest!
[14:55:11] [CRASHED]
[14:55:11] [ERROR] Test: main: missing expected subtest!
[14:55:11] [CRASHED]
[14:55:11] [ERROR] Test: main: missing expected subtest!
[14:55:11] [CRASHED]
[14:55:11] [ERROR] Test: main: missing expected subtest!
[14:55:11] [CRASHED]
[14:55:11] [ERROR] Test: main: missing expected subtest!
[14:55:11] [CRASHED]
[14:55:11] ============================================================
[14:55:11] Testing complete. Ran 62 tests: passed: 44, crashed: 16, skipped: 2, errors: 25
The kernel seems to have crashed; you can decode the stack traces with:
$ scripts/decode_stacktrace.sh .kunit/vmlinux .kunit < .kunit/test.log | tee .kunit/decoded.log | ./tools/testing/kunit/kunit.py parse
[14:55:11] Elapsed time: 16.240s total, 1.476s configuring, 14.294s building, 0.469s running
I wonder if something with my local environment is causing troubles.
next prev parent reply other threads:[~2024-05-14 22:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-14 1:08 [Bug Report] Multiple S390x KUNIT clk failures Nico Pache
2024-05-14 3:38 ` Stephen Boyd
2024-05-14 7:14 ` Nico Pache
2024-05-14 22:04 ` Stephen Boyd [this message]
[not found] ` <CAK18DXZyEHZ=1TC52kQQ89gscFLph0e_4zB_bt=DTwR-A=0UPA@mail.gmail.com>
2024-05-28 18:49 ` Donald Zickus
2024-05-28 20:49 ` Audra Mitchell
2024-05-28 22:53 ` msalter
2024-05-29 19:39 ` Stephen Boyd
2024-05-30 20:12 ` Audra Mitchell
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=9be47cd74b62ba8e4a36f3139fc8d275.sboyd@kernel.org \
--to=sboyd@kernel.org \
--cc=aubaker@redhat.com \
--cc=dzickus@redhat.com \
--cc=kunit-dev@googlegroups.com \
--cc=linux-clk@vger.kernel.org \
--cc=npache@redhat.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.