Thanks! After setting the umask and clearing Maven caches, I was able to run the integration test on two different machines.
Regards, Matthias On Tuesday, 2013-11-05, Brock Noland wrote: > I think that is caused by a bad umask. > > > On Tue, Nov 5, 2013 at 3:12 PM, Matthias Friedrich <[email protected]> wrote: > > > On Tuesday, 2013-11-05, Gabriel Reid wrote: > > > On 05 Nov 2013, at 19:38, Matthias Friedrich <[email protected]> wrote: > > [...] > > >> | Results : > > >> | > > >> | Failed tests: testCheckpoints(org.apache.crunch.CheckpointIT): > > >> | expected:<1> but was:<2> > > >> | > > >> | Tests run: 241, Failures: 1, Errors: 0, Skipped: 1 > > > > > Nope, I'm definitely not running into that issue. I took a look at the > > test > > > in question and it doesn't look like it's something that could be very > > > flaky -- looks like it'll just work (or not work) consistently. > > > > > Are you getting this repeatedly? > > > > Yep, have seen this twice today. On a different machine, I now get > > an NPE from HFileTargetIT: > > > > java.lang.NullPointerException > > at > > org.apache.hadoop.hdfs.MiniDFSCluster.startDataNodes(MiniDFSCluster.java:426) > > at > > org.apache.hadoop.hdfs.MiniDFSCluster.<init>(MiniDFSCluster.java:284) > > at > > org.apache.hadoop.hbase.HBaseTestingUtility.startMiniDFSCluster(HBaseTestingUtility.java:435) > > at > > org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:603) > > at > > org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:559) > > at > > org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:528) > > at > > org.apache.crunch.io.hbase.HFileTargetIT.setUpClass(HFileTargetIT.java:103) > > > > > > This seems vaguely familiar, I think the embedded HBase mini cluster > > requires some particular networking setup. I'll try again tomorrow. > > > > Regards, > > Matthias > > > > > > -- > Apache MRUnit - Unit testing MapReduce - http://mrunit.apache.org
