From: Bernhard Schmalhofer <[EMAIL PROTECTED]>
Date: Mon, 18 Aug 2008 14:28:47 +0200
> On Mon, Aug 18, 2008 at 4:39 AM, Patrick R. Michaud <[EMAIL PROTECTED]>
wrote:
>
>> Perhaps "make fulltest" should run the "make codetest" target instead
>> of "make codingstd_tests"?
T
Will Coleda schrieb:
On Mon, Aug 18, 2008 at 4:39 AM, Patrick R. Michaud <[EMAIL PROTECTED]> wrote:
On Sun, Aug 17, 2008 at 10:21:18PM -0400, Bob Rogers wrote:
From: James E Keenan <[EMAIL PROTECTED]>
Date: Sun, 17 Aug 2008 19:55:02 -0400
Yes, when one of the 'make codingstd_t
On Mon, Aug 18, 2008 at 4:39 AM, Patrick R. Michaud <[EMAIL PROTECTED]> wrote:
> On Sun, Aug 17, 2008 at 10:21:18PM -0400, Bob Rogers wrote:
>>From: James E Keenan <[EMAIL PROTECTED]>
>>Date: Sun, 17 Aug 2008 19:55:02 -0400
>>
>>Yes, when one of the 'make codingstd_tests' accumulates su
On Sun, Aug 17, 2008 at 10:21:18PM -0400, Bob Rogers wrote:
>From: James E Keenan <[EMAIL PROTECTED]>
>Date: Sun, 17 Aug 2008 19:55:02 -0400
>
>Yes, when one of the 'make codingstd_tests' accumulates sufficient
>PASSes, we promote it to 'make test'. Those that are not yet passing
From: James E Keenan <[EMAIL PROTECTED]>
Date: Sun, 17 Aug 2008 19:55:02 -0400
Yes, when one of the 'make codingstd_tests' accumulates sufficient
PASSes, we promote it to 'make test'. Those that are not yet passing
can generally be described as: "Requires cage-cleaner with vast
Bob Rogers wrote:
From: chromatic <[EMAIL PROTECTED]>
Date: Sun, 17 Aug 2008 09:39:05 -0700
Not all of the codingstd tests are part of make test. There's a specific
codingstd test target you can run separately. I estimate about 2/3 of the
tests will pass. The others may or ma
From: chromatic <[EMAIL PROTECTED]>
Date: Sun, 17 Aug 2008 09:39:05 -0700
Not all of the codingstd tests are part of make test. There's a specific
codingstd test target you can run separately. I estimate about 2/3 of the
tests will pass. The others may or may not ever pass. Fo
On Sunday 17 August 2008 09:29:14 Bob Rogers wrote:
>I notice that docs/project/release_manager_guide.pod says (line 123):
>
> It is not necessary to quiet all the codingstd tests for a
> release.
>
> Since these tests are on "make test" (and hence visible to
> non-developers), and
