That was it.  Thanks Alan.

-Mark

On Tue, Oct 4, 2011 at 9:37 PM, Alan Gates <[email protected]> wrote:
> You need braces around the test in your test array, as in the attached file.
>
> Alan.
>
>
>
> On Oct 4, 2011, at 6:27 PM, Mark Roddy wrote:
>
>> I'm trying to add and run a new e2e test, but I'm having trouble
>> getting it to run.  I copied one of the existing tests in nightly.conf
>> and changed the 'name' value (see attached diff).
>>
>> Next I run using the following in a bash script:
>> TESTS="-t Tokenize -t Checkin"
>> ant -Dharness.old.pig=$OLDPIG -Dharness.cluster.conf=$HCONFDIF
>> -Dharness.cluster.bin=$HBIN -Dtests.to.run="$TESTS" test-e2e-local
>>
>>
>> The output from the test run:
>>     [exec] Results so far, PASSED: 1 FAILED: 0 SKIPPED: 0 ABORTED: 0
>> FAILED DEPENDENCY: 0
>>     [exec] Results so far, PASSED: 2 FAILED: 0 SKIPPED: 0 ABORTED: 0
>> FAILED DEPENDENCY: 0
>>     [exec] Results so far, PASSED: 2 FAILED: 0 SKIPPED: 0 ABORTED: 1
>> FAILED DEPENDENCY: 0
>>     [exec] Results so far, PASSED: 2 FAILED: 0 SKIPPED: 0 ABORTED: 1
>> FAILED DEPENDENCY: 0
>>     [exec] Results so far, PASSED: 2 FAILED: 0 SKIPPED: 0 ABORTED: 1
>> FAILED DEPENDENCY: 0
>>     [exec] Results so far, PASSED: 2 FAILED: 0 SKIPPED: 0 ABORTED: 1
>> FAILED DEPENDENCY: 0
>>     [exec] Final results , PASSED: 2 FAILED: 0 SKIPPED: 0 ABORTED: 1
>> FAILED DEPENDENCY: 0
>>
>>
>> And in the log file I see this:
>> INFO TestDriver::run at 311: Running TEST GROUP(BugFix)
>> INFO TestDriver::run at 311: Running TEST GROUP(Tokenize)
>>
>> ******************************************************
>>
>> TEST: Tokenize_
>> ******************************************************
>> Beginning test Tokenize_ at 1317777576
>> ERROR TestDriver::run at : 470 Failed to run test Tokenize_
>> <TestDriverPig::runTest FATAL Did not find a testCmd that I know h\
>> ow to handle at TestDriverPig.pm line 177.
>>>
>> Results so far, PASSED: 2 FAILED: 0 SKIPPED: 0 ABORTED: 1 FAILED DEPENDENCY: >> 0
>>
>>
>> I figure I'm either specifying the test to run incorrectly, or I've
>> done something with the new test I'm added.  Any ideas?
>> <new_test.diff>
>
>
>

Reply via email to