accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-2380) Update functional test MR job to indicate failed tests
Date Thu, 20 Feb 2014 21:57:27 GMT


ASF subversion and git services commented on ACCUMULO-2380:

Commit 7059c767bfbcd2def59556ed63cdfe443f2d336b in accumulo's branch refs/heads/1.6.0-SNAPSHOT
from [~bhavanki]
[;h=7059c76 ]

ACCUMULO-2380 Improve RunTests to produce useful mapper and job output

When passed the -m option, for functional tests will emit one line on standard
output for each test that passes or fails. The output is suitable for processing when
tests are run within a mapreduce job.

The mapper for RunTests, which runs functional tests, is updated to pass -m to
It also inserts the map task attempt ID into the custom output, so that testers can trace
back any test to the task where it ran, to view its logs for example.

The mapper also now uses counters to track the number of successes, failures, errors, etc.
Note that since the job may attempt to re-run tests that error out, the total for these
counters can exceed the total number of unique tests run.

> Update functional test MR job to indicate failed tests
> ------------------------------------------------------
>                 Key: ACCUMULO-2380
>                 URL:
>             Project: Accumulo
>          Issue Type: Sub-task
>          Components: test
>    Affects Versions: 1.4.4, 1.5.0
>            Reporter: Bill Havanki
>            Assignee: Bill Havanki
>              Labels: mapreduce, test
> The MR job that runs functional tests, {{RunTests}}, does not report back on which tests
passed and failed. The mapper that runs each functional test merely outputs the text from
standard output, and the reducer is just an identity reducer. As noted in a comment:
> {code}
>     // don't do anything with the results (yet) a summary would be nice
> {code}
> Update the job to produce results that allow a tester to ascertain the pass/fail status
of each test. For example:
> * which tests passed and which failed
> * a count of pass and fail
> * which hosts ran which tests, for drilling down
> While this only applies to 1.4/1.5, it's worth checking if 1.6 has a similar capability
and the nature of its reporting.

This message was sent by Atlassian JIRA

View raw message