It seems that travis JDK 13 image got updated to early access 24 (b24) about 3 days ago. This explains why the failure started after the commit for CALCITE-2822. As Julian said, it should be related to the issues resolved in the last build [1]; not sure with which one exactly.
I've seen that Julian already took care of the failure in our test suite. Thanks! [1] https://bugs.openjdk.java.net/browse/JDK-8225198?jql=project%20%3D%20JDK%20AND%20fixVersion%20%3D%20%2213%22%20AND%20%22Resolved%20In%20Build%22%20%3D%20b24%20AND%20text%20~%20%22regex%20OR%20pattern%22%20order%20by%20component%2C%20subcomponent On Mon, Jun 10, 2019 at 10:51 AM Julian Hyde <[email protected]> wrote: > I think it is a bug in JDK 13. (Difficult to know whether it is a bug > fixed or a regression. If it’s a regression we should log a bug on the JDK.) > > Julian > > > On Jun 10, 2019, at 12:59 AM, Yuzhao Chen <[email protected]> wrote: > > > > The master branch is failing continuously, since from CALCITE-2822[1], > but I’m not sure if this commits has relationship with the failure. > > > > Siddharth and Stamatis Zampetakis, do you have any ideas ? > > > > [1] https://travis-ci.org/apache/calcite/builds/542987336 > > > > Best, > > Danny Chan >
