Hi,

During the last month some "flakiest" tests were identified. I think these
are the ones which are really break a lot. If there is no strong objection
I would create a jira for each of these (if not already exists):

org.apache.flume.source.TestSyslogUdpSource.testSourceCounter
org.apache.flume.channel.jdbc.TestJdbcChannelProvider.
testEventWithSimulatedSourceAndSinks
org.apache.flume.channel.jdbc.TestJdbcChannelProviderNoFK.
testEventWithSimulatedSourceAndSinks
org.apache.flume.sink.hbase.TestAsyncHBaseSink
org.apache.flume.sink.hbase.TestHBaseSink
org.apache.flume.source.thriftLegacy.TestThriftLegacySource
org.apache.flume.channel.TestSpillableMemoryChannel.testParallelMultipleSourcesAndSinks
(sati is already addressing this with
https://issues.apache.org/jira/browse/FLUME-2997)
org.apache.flume.sink.hdfs.TestBucketWriter.testFileSuffixGiven (bessbd is
already addressing this with
https://issues.apache.org/jira/browse/FLUME-3002)
org.apache.flume.sink.hdfs.TestBucketWriter.testFileSuffixNotGiven (bessbd
is already addressing this with
https://issues.apache.org/jira/browse/FLUME-3002)
org.apache.flume.source.TestExecSource.testMonitoredCounterGroup (mpercy is
already addressing this with https://github.com/apache/flume/pull/72)


Cheers,
Attila


On Tue, Jun 14, 2016 at 9:03 PM, Hari Shreedharan <hshreedha...@apache.org>
wrote:

> I completely agree. My best guess is that most of these are flakey tests
> due to the fact that these tests are using Thread.sleep etc. Just FYI,
> fixing all tests will probably take a lot of time.
>
> On Tue, Jun 14, 2016 at 9:40 AM Attila Simon <s...@cloudera.com> wrote:
>
> > Hi All,
> >
> > It happened to me that when I run "mvn test" target it is failing on
> > my vanilla flume repo. Also when I checked an associated jenkins job
> > (https://builds.apache.org/view/All/job/Flume-trunk-hbase-1/) it
> > showed that test wasn't green for a while. Am I doing something
> > completely wrong?
> > I suspect hadoop/hbase libs are required but I couldn't find docs
> > which would tell me what should a new joiner do to have a properly set
> > up environment? I thought maven will resolve all of the dependencies,
> > if not then what would be the recommended way to have that. Could you
> > please point me to the right direction? Every help is greatly
> > appreciated.
> >
> > If this is a known issue I would like to devote some of my time to
> > clean this up as either releasing 1.7.0 would benefit from a stable
> > tests or generally it would increase the healthiness of the whole
> > project.
> >
> > I ran tests with this command after "git clone":
> > mvn test --fail-at-end
> >
> > [INFO] Apache Flume ....................................... SUCCESS [
> > 0.365 s]
> > [INFO] Flume NG SDK ....................................... FAILURE
> [01:00
> > min]
> > [INFO] Flume NG Configuration ............................. SKIPPED
> > [INFO] Flume Auth ......................................... SKIPPED
> > [INFO] Flume NG Core ...................................... SKIPPED
> > [INFO] Flume NG Sinks ..................................... SUCCESS [
> > 0.010 s]
> > [INFO] Flume NG HDFS Sink ................................. SKIPPED
> > [INFO] Flume NG IRC Sink .................................. SKIPPED
> > [INFO] Flume NG Channels .................................. SUCCESS [
> > 0.009 s]
> > [INFO] Flume NG JDBC channel .............................. SKIPPED
> > [INFO] Flume NG file-based channel ........................ SKIPPED
> > [INFO] Flume NG Spillable Memory channel .................. SKIPPED
> > [INFO] Flume NG Node ...................................... SKIPPED
> > [INFO] Flume NG Embedded Agent ............................ SKIPPED
> > [INFO] Flume NG HBase Sink ................................ SKIPPED
> > [INFO] Flume NG ElasticSearch Sink ........................ SKIPPED
> > [INFO] Flume NG Morphline Solr Sink ....................... SKIPPED
> > [INFO] Flume Kafka Sink ................................... SKIPPED
> > [INFO] Flume NG Kite Dataset Sink ......................... SKIPPED
> > [INFO] Flume NG Hive Sink ................................. SKIPPED
> > [INFO] Flume Sources ...................................... SUCCESS [
> > 0.010 s]
> > [INFO] Flume Scribe Source ................................ SKIPPED
> > [INFO] Flume JMS Source ................................... SKIPPED
> > [INFO] Flume Twitter Source ............................... SKIPPED
> > [INFO] Flume Kafka Source ................................. SKIPPED
> > [INFO] Flume Taildir Source ............................... SKIPPED
> > [INFO] flume-kafka-channel ................................ SKIPPED
> > [INFO] Flume legacy Sources ............................... SUCCESS [
> > 0.009 s]
> > [INFO] Flume legacy Avro source ........................... SKIPPED
> > [INFO] Flume legacy Thrift Source ......................... SKIPPED
> > [INFO] Flume NG Clients ................................... SUCCESS [
> > 0.008 s]
> > [INFO] Flume NG Log4j Appender ............................ SKIPPED
> > [INFO] Flume NG Tools ..................................... SKIPPED
> > [INFO] Flume NG distribution .............................. SKIPPED
> > [INFO] Flume NG Integration Tests ......................... SKIPPED
> >
> > Environment:
> > OS X El Capitan
> > Java(TM) SE Runtime Environment (build 1.7.0_79-b15), apache flume trunk
> > set | grep -i -Ee flume\|hadoop\|hbase  => nothing
> >
> > Cheers,
> > Attila
> >
>

Reply via email to