You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@infra.apache.org by "Andrew Bayer (JIRA)" <ji...@apache.org> on 2014/10/06 21:22:34 UTC

[jira] [Commented] (INFRA-8437) HBase builds on hadoop-1 fail due to wrong umask value

    [ https://issues.apache.org/jira/browse/INFRA-8437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14160775#comment-14160775 ] 

Andrew Bayer commented on INFRA-8437:
-------------------------------------

PR up - https://github.com/apache/toolchain/pull/5

> HBase builds on hadoop-1 fail due to wrong umask value
> ------------------------------------------------------
>
>                 Key: INFRA-8437
>                 URL: https://issues.apache.org/jira/browse/INFRA-8437
>             Project: Infrastructure
>          Issue Type: Bug
>            Reporter: Ted Yu
>            Assignee: Andrew Bayer
>
> See this thread started by Lars:
> http://search-hadoop.com/m/DHED4Fls9a1/Build+machines+and+0.94&subj=Build+machines+and+0+94
> bq. Did the default umask change in the build boxes? Must have been a change that happened on October 2nd.
> bq. The umask should 022, but it looks like it's 002.
> This problem is affecting 0.98 build on hadoop-1 as well.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)