[
https://issues.apache.org/jira/browse/GORA-357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14062446#comment-14062446
]
Lewis John McGibbney commented on GORA-357:
-------------------------------------------
bq. Would it be possible to somehow check if MR testing is available?
Currently no, reason being is that it is environment specific.
Only developers are usually concerned with understanding which tests are prone
to fail e.g. TestDataFileAvroStoreMapReduce, however once you know it then you
know it. There ismaybe no more action to be taken.
Right now 'most' people following the Gora project are subscribed to dev@,
meaning that they will also see if a test is failing and the build is unstable.
I think it is a 'fair' assumption if we consider the master branch Jenkins
build as the canonical build from which we make the determination as to whether
Gora is stable or not.
Does that sound reasonable? By all means, if you are not comfortable with that,
then please suggest how we progress... in all honest I am thinking about
maintainance of a project pom.xml.
> Maven Surefire testFailureIgnore is true
> ----------------------------------------
>
> Key: GORA-357
> URL: https://issues.apache.org/jira/browse/GORA-357
> Project: Apache Gora
> Issue Type: Bug
> Components: build process
> Reporter: Tyler Palsulich
> Priority: Minor
>
> The root pom.xml file has the following line:
> {{<testFailureIgnore>true</testFailureIgnore>}}. I've noticed that some unit
> tests fail on a clean install (e.g.
> gora.avro.mapreduce.TestDataFileAvroStoreMapReduce). Is this to be expected?
--
This message was sent by Atlassian JIRA
(v6.2#6252)
