Did anything change on the build machines?
All tests runs are now failing in
TestRegionObserverScannerOpenHook.testRegionObserverCompactionTimeStacking
Caused by this:
---------------
java.lang.NullPointerException
at
org.apache.hadoop.hdfs.MiniDFSCluster.startDataNodes(MiniDFSCluster.java:422)
at org.apache.hadoop.hdfs.MiniDFSCluster.<init>(MiniDFSCluster.java:280)
at
org.apache.hadoop.hbase.HBaseTestingUtility.startMiniDFSCluster(HBaseTestingUtility.java:461)
at
org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:629)
at
org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:585)
at
org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:554)
at
org.apache.hadoop.hbase.coprocessor.TestRegionObserverScannerOpenHook.testRegionObserverCompactionTimeStacking(TestRegionObserverScannerOpenHook.java:257)
Which in turns is caused by:
----------------------------
2014-10-05 01:09:38,348 WARN [pool-1-thread-1] datanode.DataNode(1577):
Invalid directory in dfs.data.dir: Incorrect permission for
/home/jenkins/jenkins-slave/workspace/HBase-0.94-JDK7/target/test-data/735cc5bb-3e7e-442e-a8e2-dbc669e24bf3/dfscluster_b4cfbf35-fa5b-4884-9a1b-f6311a65a0a5/dfs/data/data1,
expected: rwxr-xr-x, while actual: rwxrwxr-x
2014-10-05 01:09:38,351 WARN [pool-1-thread-1] datanode.DataNode(1577):
Invalid directory in dfs.data.dir: Incorrect permission for
/home/jenkins/jenkins-slave/workspace/HBase-0.94-JDK7/target/test-data/735cc5bb-3e7e-442e-a8e2-dbc669e24bf3/dfscluster_b4cfbf35-fa5b-4884-9a1b-f6311a65a0a5/dfs/data/data2,
expected: rwxr-xr-x, while actual: rwxrwxr-x
2014-10-05 01:09:38,352 ERROR [pool-1-thread-1] datanode.DataNode(1583): All
directories in dfs.data.dir are invalid.
Did the default umask change in the build boxes? Must have been a change that
happened on October 2nd.
The umask should 022, but it looks like it's 002.
-- Lars
