This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Re: About FAILs in the internal testsuite
- From: peter wang <shangwaters at gmail dot com>
- To: David Smith <dsmith at redhat dot com>
- Cc: systemtap at sourceware dot org
- Date: Sat, 16 Apr 2016 11:52:31 +0800
- Subject: Re: About FAILs in the internal testsuite
- Authentication-results: sourceware.org; auth=none
- References: <CAP+nm+wEi=ebN5qaL0WFbb_KCK8nradFPduxstKYyrRPQ346Rw at mail dot gmail dot com> <570FDE49 dot 30400 at redhat dot com> <CAP+nm+xHFQRsYH0gjFgj7OmCmJ6ccEy5+DqK=FFGrQGvGee3Zw at mail dot gmail dot com> <5710F7F0 dot 3050208 at redhat dot com>
On Fri, Apr 15, 2016 at 10:17 PM, David Smith <dsmith@redhat.com> wrote:
> On 04/15/2016 06:03 AM, peter wang wrote:
>> Hello David,
>>
>> Thanks again for your reply.
>> There is one more thing which confused me.
>>
>> I'm not sure if I have some misunderstandings.
>> Some failures are resulted by either case's bug or systemtap's bug and
>> others should be set to KFAIL.
>>
>> In other words, all FAIL should be fixed whatever arch or system is.
>> Is that right?
>
> All FAILs should certainly be investigated to see out what is going on.
> There have been times when I've done that and left the FAIL in place.
> Here's why. In the past, I've found a few KFAIL tests that were no
> longer failing because of the orignal reason (most likely bad
> debuginfo), but failing because the underlying probe point has changed.
>
Does that mean most of the FAILs have been investigated actually?
Since investigated FAILs are still left, it is hard for others to find
the real bug, I think.
Is there any docs recording or describing the investigated FAILs?
--
Thanks
Wang
> If the problem is truly a problem in systemtap, it would be great to get
> it fixed.
>
> --
> David Smith
> dsmith@redhat.com
> Red Hat
> http://www.redhat.com
> 256.217.0141 (direct)
> 256.837.0057 (fax)