You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "Hongze Zhang (JIRA)" <ji...@apache.org> on 2019/04/06 02:48:00 UTC
[jira] [Closed] (CALCITE-2956) Jenkins failure caused by cached
classes generated by previous build
[ https://issues.apache.org/jira/browse/CALCITE-2956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hongze Zhang closed CALCITE-2956.
---------------------------------
Resolution: Fixed
I see the Jenkins CI has been changed to include clean phase, now the command starts from "mvn clean install" and the same error is no longer reported by CI. Thanks a lot for who made the change.
> Jenkins failure caused by cached classes generated by previous build
> --------------------------------------------------------------------
>
> Key: CALCITE-2956
> URL: https://issues.apache.org/jira/browse/CALCITE-2956
> Project: Calcite
> Issue Type: Bug
> Reporter: Hongze Zhang
> Priority: Major
>
> Here is the Jenkins output including the error caused by the cached class files:
> https://builds.apache.org/job/Calcite-Master/1078/jdk=JDK%201.8%20(latest),label_exp=ubuntu&&!cloud-slave&&!H27/console
> This was discussed in several threads such as [1] and [2]. Per the discussions it seems to be reasonable to change the Jenkins build command to "mvn clean verify ...".
> [1] https://lists.apache.org/thread.html/%3C455426799.3105.1552292851062.JavaMail.jenkins@jenkins02%3E
> [2]
> https://lists.apache.org/thread.html/cdf06554f83ea22a39e4133562f14e9ad5a04be6adc15e4032198c92@%3Cdev.calcite.apache.org%3E
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)