[
https://issues.apache.org/jira/browse/FLUME-935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13208265#comment-13208265
]
Juhani Connolly commented on FLUME-935:
---------------------------------------
Any idea what went wrong with the build?
The builds.apache.org link appears to be dead. I got the latest flume-728 and
applied the patch, then ran tests to get this weird result:
...
-------------------------------------------------------
T E S T S
-------------------------------------------------------
Running org.apache.flume.channel.jdbc.TestDerbySchemaHandlerQueries
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.111 sec
Running org.apache.flume.channel.jdbc.TestJdbcChannelProvider
Running org.apache.flume.channel.jdbc.TestTransactionIsolationLevelEnum
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.248 sec
Running org.apache.flume.channel.jdbc.TestPersistentEvent
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.297 sec
Running org.apache.flume.channel.jdbc.TestDatabaseTypeEnum
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.117 sec
Results :
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] Apache Flume ...................................... SUCCESS [2.380s]
[INFO] Flume NG Core ..................................... SUCCESS [1:32.000s]
[INFO] Flume NG Sinks .................................... SUCCESS [0.109s]
[INFO] Flume NG HDFS Sink ................................ SUCCESS [12.081s]
[INFO] Flume NG IRC Sink ................................. SUCCESS [0.732s]
[INFO] Flume NG Channels ................................. SUCCESS [0.037s]
[INFO] Flume NG JDBC channel ............................. FAILURE [35.217s]
[INFO] Flume NG Node ..................................... SKIPPED
[INFO] Flume NG file-based channel ....................... SKIPPED
[INFO] Flume NG distribution ............................. SKIPPED
[INFO] Flume legacy Sources .............................. SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 2:23.098s
[INFO] Finished at: Wed Feb 15 17:13:39 JST 2012
[INFO] Final Memory: 44M/179M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-surefire-plugin:2.8.1:test (default-test) on
project flume-jdbc-channel: There are test failures.
[ERROR]
[ERROR] Please refer to
/home/juhani_connolly/workspace/flume/flume-ng-channels/flume-jdbc-channel/target/surefire-reports
for the individual test results.
[ERROR] -> [Help 1]
[ERROR]
...
So the test runner gives 5 ran, 0 failures/errors/skipped but then it claims
there are failures!?
> Create abstract implementations of basic channel/transaction semantics
> ----------------------------------------------------------------------
>
> Key: FLUME-935
> URL: https://issues.apache.org/jira/browse/FLUME-935
> Project: Flume
> Issue Type: Improvement
> Components: Channel
> Affects Versions: v1.0.0
> Reporter: Peter Newcomb
> Assignee: Peter Newcomb
> Priority: Minor
> Fix For: v1.1.0
>
> Attachments: flume-935-5.patch
>
>
> Correctly executing or checking the state transitions for channels and
> transactions is nontrivial. It would be helpful to have a correct
> implementation of each that can be used either directly or as a reference
> when creating new channels or clients of channels.
> Specifically, on the client side it would be nice to package the try {
> begin() ... commit() } catch { rollback() } finally { close() } code, with
> all the appropriate exception propagation and logging code, so that it need
> not be repeated constantly.
> On the channel side, it'd be nice to have a packaged implementation of the
> implied ThreadLocal semantics of the Transaction class, along with
> Preconditions checking to make sure that clients follow the try { begin() ...
> commit() } catch { rollback() } finally { close() } pattern.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
