You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flume.apache.org by "Alexander Alten-Lorenz (JIRA)" <ji...@apache.org> on 2012/07/02 12:40:22 UTC
[jira] [Updated] (FLUME-1174) Attempt to build Flume v1.1.0 on
Windows 7 x64 fails
[ https://issues.apache.org/jira/browse/FLUME-1174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alexander Alten-Lorenz updated FLUME-1174:
------------------------------------------
Resolution: Won't Fix
Status: Resolved (was: Patch Available)
Since Flume 1.3.0-SNAPSHOT is running on Windows I mark that case as won't fix.
More details how do you get Flume running on Windows you'll found in my blog:
http://mapredit.blogspot.de/2012/07/run-flume-13x-on-windows.html
> Attempt to build Flume v1.1.0 on Windows 7 x64 fails
> ----------------------------------------------------
>
> Key: FLUME-1174
> URL: https://issues.apache.org/jira/browse/FLUME-1174
> Project: Flume
> Issue Type: Bug
> Affects Versions: v1.1.0
> Environment: Windows 7 - 64 Bit - jdk1.7u4 - mvn 3.0.4
> Reporter: Jeff Lord
> Assignee: Alexander Alten-Lorenz
> Attachments: FLUME-1174.patch, org.apache.flume.source.TestExecSource.zip
>
>
> It looks as if the src is expecting to be built on Linux.
> Attempting to build on Windows 7 fails with the below error that references a missing /etc/passwd file.
> Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.156 sec
> Running org.apache.flume.TestCounterGroup
> Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.109 sec
> Results :
> Failed tests: testRestart(org.apache.flume.source.TestExecSource)
> Tests in error:
> test(org.apache.flume.serialization.TestBodyTextEventSerializer): Unable to de
> lete file: src\test\resources\events.txt
> testProcess(org.apache.flume.source.TestExecSource): \etc\passwd (The system c
> annot find the path specified)
> Tests run: 114, Failures: 1, Errors: 2, Skipped: 2
--
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