You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flume.apache.org by "Jonathan Hsieh (JIRA)" <ji...@apache.org> on 2011/09/05 19:16:09 UTC
[jira] [Created] (FLUME-759) Regression due to avro 1.5.2 upgrade
Regression due to avro 1.5.2 upgrade
------------------------------------
Key: FLUME-759
URL: https://issues.apache.org/jira/browse/FLUME-759
Project: Flume
Issue Type: Bug
Affects Versions: v0.9.5
Reporter: Jonathan Hsieh
I've spent some time cleaning up builds and noticed that the version of maven sure fire/jenkins we were using failed to point out that the log4j appender tests have been failing since upgrading to avro 1.5.2 (FLUME-741).
This can be triggered by going into the flume-log4j-appender dir and doing a 'mvn test' in there. Test should hang or time out after 8 minute or so.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (FLUME-759) Regression due to avro 1.5.2 upgrade
Posted by "Tom White (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FLUME-759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tom White updated FLUME-759:
----------------------------
Attachment: FLUME-759.patch
This patch plus AVRO-884 fixes the problem.
> Regression due to avro 1.5.2 upgrade
> ------------------------------------
>
> Key: FLUME-759
> URL: https://issues.apache.org/jira/browse/FLUME-759
> Project: Flume
> Issue Type: Bug
> Affects Versions: v0.9.5
> Reporter: Jonathan Hsieh
> Attachments: FLUME-759.patch
>
>
> I've spent some time cleaning up builds and noticed that the version of maven sure fire/jenkins we were using failed to point out that the log4j appender tests have been failing since upgrading to avro 1.5.2 (FLUME-741).
> This can be triggered by going into the flume-log4j-appender dir and doing a 'mvn test' in there. Test should hang or time out after 8 minute or so.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (FLUME-759) Regression due to avro 1.5.2 upgrade
Posted by "Tom White (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FLUME-759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tom White updated FLUME-759:
----------------------------
Attachment: FLUME-759.patch
This patch shows that using Avro 1.5.4 (not yet released but in the staging repo) fixes the test (TestFlumeLog4jAvroAppender).
Note that this is not ready to be committed yet - we need to wait for Avro 1.5.4 to be released, and the staging repositiory should not be added to the POM.
> Regression due to avro 1.5.2 upgrade
> ------------------------------------
>
> Key: FLUME-759
> URL: https://issues.apache.org/jira/browse/FLUME-759
> Project: Flume
> Issue Type: Bug
> Affects Versions: v0.9.5
> Reporter: Jonathan Hsieh
> Attachments: FLUME-759.patch, FLUME-759.patch
>
>
> I've spent some time cleaning up builds and noticed that the version of maven sure fire/jenkins we were using failed to point out that the log4j appender tests have been failing since upgrading to avro 1.5.2 (FLUME-741).
> This can be triggered by going into the flume-log4j-appender dir and doing a 'mvn test' in there. Test should hang or time out after 8 minute or so.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (FLUME-759) Regression due to avro 1.5.2 upgrade
Posted by "Tom White (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FLUME-759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tom White updated FLUME-759:
----------------------------
Assignee: Tom White
Status: Patch Available (was: Open)
> Regression due to avro 1.5.2 upgrade
> ------------------------------------
>
> Key: FLUME-759
> URL: https://issues.apache.org/jira/browse/FLUME-759
> Project: Flume
> Issue Type: Bug
> Affects Versions: v0.9.5
> Reporter: Jonathan Hsieh
> Assignee: Tom White
> Attachments: FLUME-759.patch, FLUME-759.patch, FLUME-759.patch
>
>
> I've spent some time cleaning up builds and noticed that the version of maven sure fire/jenkins we were using failed to point out that the log4j appender tests have been failing since upgrading to avro 1.5.2 (FLUME-741).
> This can be triggered by going into the flume-log4j-appender dir and doing a 'mvn test' in there. Test should hang or time out after 8 minute or so.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (FLUME-759) Regression due to avro 1.5.2 upgrade
Posted by "Jonathan Hsieh (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FLUME-759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Hsieh updated FLUME-759:
---------------------------------
Resolution: Fixed
Fix Version/s: v0.9.5
Status: Resolved (was: Patch Available)
committed. Thanks tom!
> Regression due to avro 1.5.2 upgrade
> ------------------------------------
>
> Key: FLUME-759
> URL: https://issues.apache.org/jira/browse/FLUME-759
> Project: Flume
> Issue Type: Bug
> Affects Versions: v0.9.5
> Reporter: Jonathan Hsieh
> Assignee: Tom White
> Fix For: v0.9.5
>
> Attachments: FLUME-759.patch, FLUME-759.patch, FLUME-759.patch
>
>
> I've spent some time cleaning up builds and noticed that the version of maven sure fire/jenkins we were using failed to point out that the log4j appender tests have been failing since upgrading to avro 1.5.2 (FLUME-741).
> This can be triggered by going into the flume-log4j-appender dir and doing a 'mvn test' in there. Test should hang or time out after 8 minute or so.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (FLUME-759) Regression due to avro 1.5.2 upgrade
Posted by "Jonathan Hsieh (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FLUME-759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13097218#comment-13097218 ]
Jonathan Hsieh commented on FLUME-759:
--------------------------------------
FLUME-755 (upgrading to avro 1.5.3) did not fix this problem.
> Regression due to avro 1.5.2 upgrade
> ------------------------------------
>
> Key: FLUME-759
> URL: https://issues.apache.org/jira/browse/FLUME-759
> Project: Flume
> Issue Type: Bug
> Affects Versions: v0.9.5
> Reporter: Jonathan Hsieh
>
> I've spent some time cleaning up builds and noticed that the version of maven sure fire/jenkins we were using failed to point out that the log4j appender tests have been failing since upgrading to avro 1.5.2 (FLUME-741).
> This can be triggered by going into the flume-log4j-appender dir and doing a 'mvn test' in there. Test should hang or time out after 8 minute or so.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (FLUME-759) Regression due to avro 1.5.2 upgrade
Posted by "Tom White (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FLUME-759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tom White updated FLUME-759:
----------------------------
Attachment: FLUME-759.patch
Here's a new patch now that Avro 1.5.4 is in Maven central. I also fixed a couple of places where the 1.5.3 Avro Maven plugin was being used.
> Regression due to avro 1.5.2 upgrade
> ------------------------------------
>
> Key: FLUME-759
> URL: https://issues.apache.org/jira/browse/FLUME-759
> Project: Flume
> Issue Type: Bug
> Affects Versions: v0.9.5
> Reporter: Jonathan Hsieh
> Attachments: FLUME-759.patch, FLUME-759.patch, FLUME-759.patch
>
>
> I've spent some time cleaning up builds and noticed that the version of maven sure fire/jenkins we were using failed to point out that the log4j appender tests have been failing since upgrading to avro 1.5.2 (FLUME-741).
> This can be triggered by going into the flume-log4j-appender dir and doing a 'mvn test' in there. Test should hang or time out after 8 minute or so.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira