All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Bligh <mbligh@google.com>
To: subrata@linux.vnet.ibm.com
Cc: Mike Frysinger <vapier@gentoo.org>,
	ltp-list <ltp-list@lists.sf.net>,
	sudhir kumar <smalikphy@gmail.com>,
	Autotest mailing list <autotest@test.kernel.org>,
	Lucas Meneghel Rodrigues <mrodrigu@redhat.com>,
	Uri Lublin <uril@redhat.com>, kvm-devel <kvm@vger.kernel.org>
Subject: Re: [PATCH 1/2] Add latest LTP test in autotest
Date: Wed, 8 Jul 2009 08:05:33 -0700	[thread overview]
Message-ID: <33307c790907080805r78016b3cl21b065e2a0d50c3b@mail.gmail.com> (raw)
In-Reply-To: <1247048369.5405.35.camel@subratamodak.linux.ibm.com>

>> Yup, we can pass an excluded test list. I really wish they'd fix their
>> tests, but I've been saying that for 6 years now, and it hasn't happened
>> yet ;-(
>
> I would slightly disagree to that. 6 years is history. But, have you
> recently checked with LTP ?

I hate to be completely cynical about this, but that's exactly the same
message I get every year.

Yes, absolute, the best thing would be for someone to run all the tests,
work through all the problems, categorize them as kernel / library / distro,
and get each of them fixed. However, it's a fair chunk of work that I don't
have time to do.

So all I'm saying is that I know which of the current tests we have issues
with, and I don't want to upgrade LTP without a new set of data, and that
work being done. From previous experience, I would be extremely
surprised if there's not at least one new problem, and I'm not just going
to dump that on users.

Does the LTP project do this itself on a regular basis ... ie are you running
LTP against the latest kernel (or even some known stable kernel) and
seeing which tests are broken? If you can point me to that, I'd have much
more faith about picking this up ...

Up until this point we've not even managed to agree that PASS means
"ran as expected" and FAIL meant "something is wrong". LTP always
had "expected failures" which seems like a completely broken model
to me.

M.

WARNING: multiple messages have this Message-ID (diff)
From: Martin Bligh <mbligh@google.com>
To: subrata@linux.vnet.ibm.com
Cc: ltp-list <ltp-list@lists.sf.net>,
	Mike Frysinger <vapier@gentoo.org>,
	kvm-devel <kvm@vger.kernel.org>,
	Lucas Meneghel Rodrigues <mrodrigu@redhat.com>,
	Autotest mailing list <autotest@test.kernel.org>,
	Uri Lublin <uril@redhat.com>, sudhir kumar <smalikphy@gmail.com>
Subject: Re: [LTP] [PATCH 1/2] Add latest LTP test in autotest
Date: Wed, 8 Jul 2009 08:05:33 -0700	[thread overview]
Message-ID: <33307c790907080805r78016b3cl21b065e2a0d50c3b@mail.gmail.com> (raw)
In-Reply-To: <1247048369.5405.35.camel@subratamodak.linux.ibm.com>

>> Yup, we can pass an excluded test list. I really wish they'd fix their
>> tests, but I've been saying that for 6 years now, and it hasn't happened
>> yet ;-(
>
> I would slightly disagree to that. 6 years is history. But, have you
> recently checked with LTP ?

I hate to be completely cynical about this, but that's exactly the same
message I get every year.

Yes, absolute, the best thing would be for someone to run all the tests,
work through all the problems, categorize them as kernel / library / distro,
and get each of them fixed. However, it's a fair chunk of work that I don't
have time to do.

So all I'm saying is that I know which of the current tests we have issues
with, and I don't want to upgrade LTP without a new set of data, and that
work being done. From previous experience, I would be extremely
surprised if there's not at least one new problem, and I'm not just going
to dump that on users.

Does the LTP project do this itself on a regular basis ... ie are you running
LTP against the latest kernel (or even some known stable kernel) and
seeing which tests are broken? If you can point me to that, I'd have much
more faith about picking this up ...

Up until this point we've not even managed to agree that PASS means
"ran as expected" and FAIL meant "something is wrong". LTP always
had "expected failures" which seems like a completely broken model
to me.

M.

------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge  
This is your chance to win up to $100,000 in prizes! For a limited time, 
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize  
details at: http://p.sf.net/sfu/Challenge
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

  reply	other threads:[~2009-07-08 15:05 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-06  5:40 [AUTOTEST] [PATCH 1/2] Add latest LTP test in autotest sudhir kumar
2009-07-06  6:58 ` Lucas Meneghel Rodrigues
2009-07-06 18:37   ` [Autotest] " Martin Bligh
2009-07-07  7:24     ` sudhir kumar
2009-07-07 15:31       ` Lucas Meneghel Rodrigues
2009-07-08  4:22         ` sudhir kumar
2009-07-08  4:40           ` Martin Bligh
2009-07-08  9:25             ` Dor Laor
2009-07-08  9:30               ` sudhir kumar
2009-07-07 17:45       ` Martin Bligh
2009-07-08  4:17         ` sudhir kumar
2009-07-08 10:19           ` Subrata Modak
2009-07-08 10:19         ` Subrata Modak
2009-07-08 10:19           ` [LTP] " Subrata Modak
2009-07-08 15:05           ` Martin Bligh [this message]
2009-07-08 15:05             ` Martin Bligh
2009-07-08 23:05           ` Mike Frysinger
2009-07-08 23:05             ` [LTP] " Mike Frysinger
2009-07-13  4:45     ` [Autotest] [AUTOTEST] " sudhir kumar

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=33307c790907080805r78016b3cl21b065e2a0d50c3b@mail.gmail.com \
    --to=mbligh@google.com \
    --cc=autotest@test.kernel.org \
    --cc=kvm@vger.kernel.org \
    --cc=ltp-list@lists.sf.net \
    --cc=mrodrigu@redhat.com \
    --cc=smalikphy@gmail.com \
    --cc=subrata@linux.vnet.ibm.com \
    --cc=uril@redhat.com \
    --cc=vapier@gentoo.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.