[
https://issues.apache.org/jira/browse/FLUME-1174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13267698#comment-13267698
]
Harsh J commented on FLUME-1174:
--------------------------------
Yeah for the first failure at TestExecSource, we should just use another well
known, constant and readable file instead of /etc/passwd. And something that
works across platform. That would best be: A file of our own?
Its the test itself at fault, I wouldn't say its Windows at fault there. We
should definitely allow Windows to build Flume if we can. Of course, this is
just tests oddly failing, doesn't mean the core build itself fails. Skipping
tests should reveal major issues.
For the second failure, is the issue with Commons' FileUtils.forceDelete? Is
that not guaranteed to work on Windows? Why are we using that instead of
regular File API deletes though? I don't see permissions being messed with/etc.
:)
> 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
>
> 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
