[TEST] testCrossJoinAsteriskQuery had incorrect expected results.  We were seeing 2 different results when this test was run depending on whether the {[Time].[1997].children} set was cached from a previous query or not.  If the test was run individually we were seeing the incorrect results, which matched the expecteds.
 The bad results are caused by MONDRIAN-2138, which is a native eval bug that can occur when .children is used on a non-all default member.  Side-stepped this bug by removing NON EMPTY from the axis.
Merge pull request #339 from mkambol/testAster

[TEST] testCrossJoinAsteriskQuery had incorrect expected results.  We we...