[
https://issues.apache.org/jira/browse/MAPREDUCE-839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12750017#action_12750017
]
Hong Tang commented on MAPREDUCE-839:
-------------------------------------
bq. I'd be happier driving this from JVM properties than env variables, as its
easier to set up JVM properties under a debugger or from build.properties.
The reason I choose to inspect env variables TEMP and TMP is because if they
are set, we should try to honor those locations. But I am fine to support using
JVM properties (in case altering the global TMP/TEMP would affect other test
cases).
bq. Assuming <junit> is forking, you can set up env variables to pass down
Not quite clear what you mean, do you suggest to test whether the
aforementioned properties are set, and if so, set env variables TEMP and TMP to
those values?
> unit test TestMiniMRChildTask fails on mac os-x
> -----------------------------------------------
>
> Key: MAPREDUCE-839
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-839
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Affects Versions: 0.21.0
> Reporter: Hong Tang
> Assignee: Hong Tang
> Priority: Minor
> Fix For: 0.21.0
>
> Attachments: mapreduce-839-20090828.patch
>
>
> The unit test TestMiniMRChildTask fails on Mac OS-X (10.5.8)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
