Re: [jdt-dev] [platform-dev] Gerrit Builds are Failing

["Daniel Megert" <daniel_megert@xxxxxxxxxx>]

What was the issue?

Dani



From:
       "Sravan
K Lakkimsetti" <sravankumarl@xxxxxxxxxx>
To:
       "Eclipse
JDT general developers list." <jdt-dev@xxxxxxxxxxx>, "Eclipse
       platform general developers list."
<platform-dev@xxxxxxxxxxx>
Date:
       24.12.2019
11:28
Subject:
       [EXTERNAL]
Re: [platform-dev] [jdt-dev] Gerrit Builds are Failing
Sent
by:        platform-dev-bounces@xxxxxxxxxxx

---

I removed I20191223-1800 (lastnight’s I build) from the repository. Please try again. Now the build should use I20191222-1800 build

 

Thanks

Sravan

 

From:Ed Merks <ed.merks@xxxxxxxxx>
Sent: 24 December 2019 15:27
To: jdt-dev@xxxxxxxxxxx; Eclipse platform general developers list. <platform-dev@xxxxxxxxxxx>
Subject: [EXTERNAL] [jdt-dev] Gerrit Builds are Failing

 

Gerrit Builds are failing, e.g., 
https://ci.eclipse.org/jdt/job/eclipse.jdt.core-Gerrit/2556/console
https://ci.eclipse.org/equinox/job/p2-gerrit/2573/console
I assume all Platform Gerrit verification
builds will fail this same way.
The stack traces look like this:
10:27:10[INFO] 
10:27:10[INFO] --- tycho-eclipserun-plugin:1.6.0-SNAPSHOT:eclipse-run (api-analysis)
@ org.eclipse.jdt.core ---
10:27:10[INFO] Toolchain in tycho-eclipserun-plugin: JDK[/opt/tools/java/oracle/jdk-8/latest/jre]
10:27:10[INFO] Expected eclipse log file: /home/jenkins/agent/workspace/eclipse.jdt.core-Gerrit/org.eclipse.jdt.core/target/eclipserun-work/data/.metadata/.log
10:27:10[INFO] Command line:
10:27:10 [/opt/tools/java/oracle/jdk-8/latest/jre/bin/java, -Xmx2048M, -jar,
/home/jenkins/agent/workspace/eclipse.jdt.core-Gerrit/.repository/p2/osgi/bundle/org.eclipse.equinox.launcher/1.5.600.v20191014-2022/org.eclipse.equinox.launcher-1.5.600.v20191014-2022.jar,
-install, /home/jenkins/agent/workspace/eclipse.jdt.core-Gerrit/org.eclipse.jdt.core/target/eclipserun-work,
-configuration, /home/jenkins/agent/workspace/eclipse.jdt.core-Gerrit/org.eclipse.jdt.core/target/eclipserun-work/configuration,
-data, /home/jenkins/agent/workspace/eclipse.jdt.core-Gerrit/org.eclipse.jdt.core/../target/org.eclipse.jdt.core-apiAnalyzer-workspace,
-application, org.eclipse.pde.api.tools.apiAnalyzer, -project, /home/jenkins/agent/workspace/eclipse.jdt.core-Gerrit/org.eclipse.jdt.core,
-baseline, /home/jenkins/agent/workspace/eclipse.jdt.core-Gerrit/org.eclipse.jdt.core/target/org.eclipse.jdt.core-apiBaseline.target,
-dependencyList, /home/jenkins/agent/workspace/eclipse.jdt.core-Gerrit/org.eclipse.jdt.core/target/dependencies-list.txt,
-failOnError]
10:28:03org.eclipse.core.internal.resources.ResourceException: Errors occurred
during the build.
10:28:03 at org.eclipse.core.internal.resources.Project$1.run(Project.java:568)
10:28:03 at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2292)
10:28:03 at org.eclipse.core.internal.resources.Project.internalBuild(Project.java:603)
10:28:03 at org.eclipse.core.internal.resources.Project.build(Project.java:116)
10:28:03 at org.eclipse.pde.api.tools.internal.ApiAnalysisApplication.start(ApiAnalysisApplication.java:128)
10:28:03 at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:203)
10:28:03 at org.eclipse.equinox.internal.app.AnyThreadAppLauncher.run(AnyThreadAppLauncher.java:30)
10:28:03 at java.lang.Thread.run(Thread.java:748)
10:28:03Contains: Errors running builder 'Java Builder' on project 'org.eclipse.jdt.core'.
10:28:03java.lang.ClassCastException: org.eclipse.jdt.internal.compiler.ast.MessageSend
cannot be cast to org.eclipse.jdt.internal.compiler.ast.AllocationExpression
10:28:03 at org.eclipse.jdt.internal.compiler.ast.FakedTrackingVariable.cleanUpAfterAssignment(FakedTrackingVariable.java:702)
10:28:03 at org.eclipse.jdt.internal.compiler.ast.Assignment.analyseCode(Assignment.java:89)
10:28:03 at org.eclipse.jdt.internal.compiler.ast.Block.analyseCode(Block.java:48)
10:28:03 at org.eclipse.jdt.internal.compiler.ast.IfStatement.analyseCode(IfStatement.java:109)
10:28:03 at org.eclipse.jdt.internal.compiler.ast.Block.analyseCode(Block.java:48)
10:28:03 at org.eclipse.jdt.internal.compiler.ast.TryStatement.analyseCode(TryStatement.java:182)
10:28:03 at org.eclipse.jdt.internal.compiler.ast.Block.analyseCode(Block.java:48)
10:28:03 at org.eclipse.jdt.internal.compiler.ast.ForeachStatement.analyseCode(ForeachStatement.java:133)
10:28:03 at org.eclipse.jdt.internal.compiler.ast.Block.analyseCode(Block.java:48)
10:28:03 at org.eclipse.jdt.internal.compiler.ast.IfStatement.analyseCode(IfStatement.java:109)
10:28:03 at org.eclipse.jdt.internal.compiler.ast.LabeledStatement.analyseCode(LabeledStatement.java:58)
10:28:03 at org.eclipse.jdt.internal.compiler.ast.Block.analyseCode(Block.java:48)
10:28:03 at org.eclipse.jdt.internal.compiler.ast.IfStatement.analyseCode(IfStatement.java:109)
10:28:03 at org.eclipse.jdt.internal.compiler.ast.Block.analyseCode(Block.java:48)
10:28:03 at org.eclipse.jdt.internal.compiler.ast.TryStatement.analyseCode(TryStatement.java:182)
10:28:03 at org.eclipse.jdt.internal.compiler.ast.MethodDeclaration.analyseCode(MethodDeclaration.java:128)
10:28:03 at org.eclipse.jdt.internal.compiler.ast.TypeDeclaration.internalAnalyseCode(TypeDeclaration.java:774)
10:28:03 at org.eclipse.jdt.internal.compiler.ast.TypeDeclaration.analyseCode(TypeDeclaration.java:272)
10:28:03 at org.eclipse.jdt.internal.compiler.ast.CompilationUnitDeclaration.analyseCode(CompilationUnitDeclaration.java:132)
10:28:03 at org.eclipse.jdt.internal.compiler.Compiler.process(Compiler.java:907)
10:28:03 at org.eclipse.jdt.internal.compiler.ProcessTaskManager.run(ProcessTaskManager.java:145)
10:28:03 at java.lang.Thread.run(Thread.java:748)
I believe I've tracked the problem down
to the merged change related to bug 463320, merged yesterday and built
last night.  I've describe the details in this comment:
  https://bugs.eclipse.org/bugs/show_bug.cgi?id=463320#c19
I've contributed what I'm pretty sure
is the fix:
  https://git.eclipse.org/r/#/c/155009/
But ironically that verification build
fails because it's using last-night's broken version of JDT to do api-analysis.
 Somehow this commit will needs to be merged without first passing
a verification build.  
And of course I wonder if (worry that)
the normal integration builds also do api-analysis and will also fail,
leaving us unable to fix this problem without some type of manual intervention.
Regards,
Ed
_______________________________________________
platform-dev mailing list
platform-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://www.eclipse.org/mailman/listinfo/platform-dev