From: William Cohen <wcohen@redhat.com>
To: Martin Cermak <mcermak@redhat.com>
Cc: wcohen@redhat.com, systemtap@sourceware.org
Subject: Re: Systmetap Testsuite results and areas to fix
Date: Fri, 3 Nov 2023 13:42:08 -0400 [thread overview]
Message-ID: <6b91a0f0-174f-482c-981d-0bbd4e5c0352@redhat.com> (raw)
In-Reply-To: <20231103145821.ekt5wler6r74yqyj@lida.tpb.lab.eng.brq.redhat.com>
On 11/3/23 10:58, Martin Cermak wrote:
> On Thu 2023-11-02 13:48 , William Cohen via Systemtap wrote:
>> Overall on x86_64 RHEL8/RHEL9/F38/rawhide the systemtap testsuite
>> complete. There are still on the order of 1500 failures on the x86_64
>> machine, which is more than desired.
>>
>> I went looking for failures/issues in the testsuite that cause multiple
>> failures in the the test results. For example previously fixed
>> runtime to avoid conflicts with added glibc functions to allow dyninst
>> code to build without error on Fedora rawhide and turn off gcc warning
>> about string ops for the syscall tests to allow the test to be built.
>>
>> - A number of the syscall test fail because the syscall string
>> argument is not properly fetched and printed. This appears to be a
>> large portion of the 700 syscall.exp failures.
>>
>>
>> - About 200 of the "listing_mode" tests fail. They all reported:
>>
>> received: "child process exited abnormally"
>>
>> Going to investigate this more closely.
I tracked this down to DWARF5 call site information being different than DWARF4 (pr31028). A fix has been pushed upstream for this and should eliminate these (and some other failures).
>>
>>
>> - About 150 of the tracepoints_list tests fail. Most are reporting
>> "not found by systemtap" but a few ('dlm', sof', and 'sof_int') fail
>> compilation because headers are not found.
>>
>>
>> - Approximately 130 failures in the tapset_functions.exp tests.
>> This looks like an issue with the test itself rather than
>> systemtap. A lot of messages of the form:
>>
>> FAIL: tapset_functions_stress (list_values(unknown))
>> FAIL: tapset_functions_stress (default_value(unknown))
>
> I've looked into this one. I've found some issues there, but
> none of them appeared to be a systemtap bug. After checking with
> Frank on the channel, however, I've dropped this testcase entirely.
>
> m.
The elimination of tapset_functions.exp test and addition of the DWARF5 callee will reduce the number of FAILs significantly.
-Will>>
>> Think this might have been by conscious language initiative changes
>> (d1804e051dd) around november 2020. Going to check to see if
>> systemtap-4.4 built before these patches has the
>> systemtap.stress/tapset_functions.exp test work.
>>
>> -Will
>>
>
next prev parent reply other threads:[~2023-11-03 17:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-02 17:48 William Cohen
2023-11-03 14:58 ` Martin Cermak
2023-11-03 17:42 ` William Cohen [this message]
2023-11-03 18:08 ` William Cohen
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=6b91a0f0-174f-482c-981d-0bbd4e5c0352@redhat.com \
--to=wcohen@redhat.com \
--cc=mcermak@redhat.com \
--cc=systemtap@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).