Github user bzz commented on the issue:
https://github.com/apache/zeppelin/pull/1668
2 Scala 2.11 profiles failed on IgniteSQL tests - a flaky test tracked
under [ZEPPELIN-1738](https://issues.apache.org/jira/browse/ZEPPELIN-1738l)
```
Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 1.116 sec
<<< FAILURE! - in org.apache.zeppelin.ignite.IgniteSqlInterpreterTest
testSql(org.apache.zeppelin.ignite.IgniteSqlInterpreterTest) Time elapsed:
0.909 sec <<< FAILURE!
java.lang.AssertionError: expected:<SUCCESS> but was:<ERROR>
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:743)
at org.junit.Assert.assertEquals(Assert.java:118)
at org.junit.Assert.assertEquals(Assert.java:144)
at
org.apache.zeppelin.ignite.IgniteSqlInterpreterTest.testSql(IgniteSqlInterpreterTest.java:95)
Results :
Failed tests:
IgniteSqlInterpreterTest.testSql:95 expected:<SUCCESS> but was:<ERROR>
Tests run: 4, Failures: 1, Errors: 0, Skipped: 0
```
which is not relevant to the change.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
