There’s another thing. My build scripts check for deprecation warnings and this one has been occurring for a few days.
> [WARNING] > /home/jhyde/regress/calcite/core/src/main/java/org/apache/calcite/adapter/enumerable/PhysTypeImpl.java:[238,21] > > convertTo(org.apache.calcite.linq4j.tree.Expression,org.apache.calcite.adapter.enumerable.PhysType) > in org.apache.calcite.adapter.enumerable.PhysType has been deprecated Maybe mine is the only script that sees this, but it’s been bugging me. I’ll fix it directly after the release. Julian > On Mar 12, 2019, at 8:22 PM, Hongze Zhang <[email protected]> wrote: > > The same problem happens again on a slave node ubuntu-1[1] at time > 2019-3-12T18:19:10Z, and I am going to wipe out Calcite's workspace of this > machine. > > By the way, does anyone know the reason of not including a maven "clean" > phase before executing "mvn verify" in the Jenkins build configuration? > > > Best, > Hongze > > > [1] > https://builds.apache.org/job/Calcite-Master/jdk=JDK%201.8%20(latest),label_exp=ubuntu&&!cloud-slave&&!H27/ > > > > ------ Original Message ------ > From: "Stamatis Zampetakis" <[email protected]> > To: [email protected] > Sent: 2019/3/12 0:56:36 > Subject: Re: Calcite-Master - Build # 1070 - Still Failing > >> Thanks for looking into this Hongze. >> >> Unfortunately I am not really familiar with the CI either so I cannot >> answer your question. >> >> In general, I am a bit surprised that there are classes which remain from >> one build to the other but I guess this is not due to the previous commit >> but a more general problem. >> >> >> >> >> On Mon, Mar 11, 2019, 12:16 PM Hongze Zhang <[email protected]> wrote: >> >>> Hi Stamatis, >>> >>> I am not much familiar with Calcite's Jenkins CI currently, but I can >>> see the reason of the build error is that some cached classes generated >>> by old code reference the class SequencedAdderAggregateLambdaFactory >>> that has been renamed already. >>> >>> I have wiped out the workspace on slave nodes H20, H22, H24, now during >>> the latest build the error seems went away[1]. But do you or anyone know >>> a way to clean the workspace on all possible build slave nodes? I am not >>> sure if what I have done is enough to prevent that the same problem >>> occurs again. >>> >>> Best, >>> Hongze >>> >>> >>> [1] https://builds.apache.org/job/Calcite-Master/1072/ >>> >>> ------ Original Message ------ >>> From: "Hongze Zhang" <[email protected]> >>> To: [email protected] >>> Sent: 2019/3/11 17:42:43 >>> Subject: Re: Calcite-Master - Build # 1070 - Still Failing >>> >>> >Stamatis, >>> > >>> >Thank you for reminding me, working on finding a reason. >>> > >>> >Best, >>> >Hongze >>> > >>> >------ Original Message ------ >>> >From: "Stamatis Zampetakis" <[email protected]> >>> >To: [email protected] >>> >Sent: 2019/3/11 17:05:12 >>> >Subject: Re: Calcite-Master - Build # 1070 - Still Failing >>> > >>> >>Jenkis fails quite often lately and many times with the following error: >>> >> >>> >>java.lang.ClassNotFoundException: >>> >>> >>org.apache.calcite.adapter.enumerable.SequencedAdderAggregateLambdaFactory >>> >> >>> >>It seems related with the following commit: >>> >> >>> >> >>> https://github.com/apache/calcite/commit/f992e6c8fbc3712c6bd70096fb6b05da448b2cab >>> >> >>> >>where this class was renamed. >>> >> >>> >>Can you please have a look Hongze Zhang? >>> >> >>> >>Best, >>> >>Stamatis >>> >> >>> >> >>> >> >>> >> >>> >>Στις Δευ, 11 Μαρ 2019 στις 9:27 π.μ., ο/η Apache Jenkins Server < >>> >>[email protected]> έγραψε: >>> >> >>> >>> The Apache Jenkins build system has built Calcite-Master (build #1070) >>> >>> >>> >>> Status: Still Failing >>> >>> >>> >>> Check console output at >>> https://builds.apache.org/job/Calcite-Master/1070/ >>> >>> to view the results. >>> >> >> >
