+
Sandy Ryza 2013-02-26, 00:45
-
Re: tests in mapreduce.lib excluded in jenkins?Robert Evans 2013-02-26, 15:10
All of the pre-commit builds only run tests for the projects that had
changes. This is a known issue, but was done because the pre-commit
builds were taking a very long time. There have been a few proposals to
improve the situation, like having any change in map/reduce run all of the
map/reduce tests instead of just a sub set of them (sorry JIRA is acting
up right now so I don't have a reference to the JIRA number). But none of
them have gone in yet.
--Bobby
On 2/25/13 6:45 PM, "Sandy Ryza" <[EMAIL PROTECTED]> wrote:
>A recent patch of mine
>(https://issues.apache.org/jira/browse/MAPREDUCE-4994)
>broke a couple of tests, but the Hadoop QA build (
>https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/3321/testReport/)
>didn't
>catch anything wrong. It looks like the tests under mapred.lib and
>mapreduce.lib, such as TestChainMapReduce and TestLineRecordReader aren't
>running. Is this intentional?
>
>thanks,
>Sandy
changes. This is a known issue, but was done because the pre-commit
builds were taking a very long time. There have been a few proposals to
improve the situation, like having any change in map/reduce run all of the
map/reduce tests instead of just a sub set of them (sorry JIRA is acting
up right now so I don't have a reference to the JIRA number). But none of
them have gone in yet.
--Bobby
On 2/25/13 6:45 PM, "Sandy Ryza" <[EMAIL PROTECTED]> wrote:
>A recent patch of mine
>(https://issues.apache.org/jira/browse/MAPREDUCE-4994)
>broke a couple of tests, but the Hadoop QA build (
>https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/3321/testReport/)
>didn't
>catch anything wrong. It looks like the tests under mapred.lib and
>mapreduce.lib, such as TestChainMapReduce and TestLineRecordReader aren't
>running. Is this intentional?
>
>thanks,
>Sandy
