Re: [jdt-dev] build trouble

[Jayaprakash Arthanareeswaran <jarthana@xxxxxxxxxx>]

> Is it possible to create an aggregated, sorted list of all pr-builds??

Does this help?
https://ci.eclipse.org/jdt/job/eclipse.jdt.core-Github/view/change-requests/builds

Regards,
Jay

-----Original Message-----
From: jdt-dev <jdt-dev-bounces@xxxxxxxxxxx> On Behalf Of Stephan Herrmann
Sent: 26 April 2022 16:06
To: jdt-dev@xxxxxxxxxxx
Subject: [EXTERNAL] Re: [jdt-dev] build trouble

The problems seem to run deeper than I thought.

(1) the immediate crash of "eclipse-run (build-.api_description)" no longer happens. I still wonder, how this could happen, and not knowing the cause leaves an uneasy feeling. Anyway, it's not longer the main concern.

(2) the timeout in builds persists for my pull request [1], and while I was puzzled, how my changes could possibly cause such a freeze, I finally found another, unrelated build that failed with the exact same freeze [2]. As that problem never occurs when running tests in the IDE, I started to spam the code with sysouts. My results so far can be found in [3], but so far I'm still clueless about the reason of these freezes. TL;DR: searching never returns from engine.searchAllTypeNames(), which looks quite severe to me.

(3) I tried to go the extra mile and debug this using a local maven build, but didn't get beyond this:

[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-enforcer-plugin:3.0.0:enforce
(no-tabs-in-compiler-messages) on project org.eclipse.jdt.core: Unable to parse configuration of mojo org.apache.maven.plugins:maven-enforcer-plugin:3.0.0:enforce for parameter
evaluateBeanshell: Cannot create instance of class
org.apache.maven.plugins.enforcer.EvaluateBeanshell: bsh/EvalError: 
bsh.EvalError -> [Help 1]

(3.1) Does anyone know of a magic incantation that allows running maven with only minimal steps to build and test, ignoring all those enforce-this, check-that, compare-whatnot tasks?

(4) When I first encountered the freezes, I started looking into other builds, if any of those are affected as well, but since we no longer have a combined list of gerrit builds, it is very hard to observe general health of our builds and detect since when exactly a certain general failure occurs. Is it possible to create an aggregated, sorted list of all pr-builds??


All these together make further JDT/Core development impossible for the time being. Are other JDT components affected as well?

Stephan



[1] https://github.com/eclipse-jdt/eclipse.jdt.core/pull/28
[2] https://github.com/eclipse-jdt/eclipse.jdt.core/pull/38
[3] https://github.com/eclipse-jdt/eclipse.jdt.core/pull/38#issuecomment-1108703551 

On 22.04.22 00:15, Stephan Herrmann wrote:
> These days I'm having tremendous problems with jenkins, for a change.
> 
> See
> https://ci.eclipse.org/jdt/job/eclipse.jdt.core-Github/view/change-req
> uests/job/PR-28/
> 
> 
> The first runs repeatably aborted just after suite ASTConverterTest2.
> At that point the test suite just dropped silent waiting for the 
> timeout (while locally in the IDE all these tests run fine).
> 
> Next I pushed some sysout for debugging that issue.  Since then the 
> job didn't even succeed to build any more, saying:
> 
> 20:51:46  [ERROR] Failed to execute goal 
> org.eclipse.tycho.extras:tycho-eclipserun-plugin:3.0.0-SNAPSHOT:eclips
> e-run
> (build-.api_description) on project org.eclipse.jdt.annotation: Error 
> while executing platform: Error while executing platform: return 
> code=13, see content of 
> /home/jenkins/agent/workspace/eclipse.jdt.core-Github_PR-28/org.eclips
> e.jdt.annotation/target/apigeneration-workspace/data/.metadata/.logfor
> more details. -> [Help 1]
> 20:51:46  [ERROR] Failed to execute goal 
> org.eclipse.tycho.extras:tycho-eclipserun-plugin:3.0.0-SNAPSHOT:eclips
> e-run
> (build-.api_description) on project org.eclipse.jdt.annotation: Error 
> while executing platform: Error while executing platform: return 
> code=13, see content of 
> /home/jenkins/agent/workspace/eclipse.jdt.core-Github_PR-28/org.eclips
> e.jdt.annotation_v1/target/apigeneration-workspace/data/.metadata/.log
> for
> more details. -> [Help 1]
> 20:51:46  [ERROR] Failed to execute goal 
> org.eclipse.tycho.extras:tycho-eclipserun-plugin:3.0.0-SNAPSHOT:eclips
> e-run
> (build-.api_description) on project org.eclipse.jdt.core: Error while 
> executing
> platform: Error while executing platform: return code=13, see content 
> of 
> /home/jenkins/agent/workspace/eclipse.jdt.core-Github_PR-28/org.eclips
> e.jdt.core/target/apigeneration-workspace/data/.metadata/.logfor
> more details. -> [Help 1]
> 
> Anybody else seeing this?
> Anybody else missing the jenkins workspace where we could inspect the logs???
> 
> Needless to say, that I didn't touch anything in 
> org.eclipse.jdt.annotation. So why is it's build crashing now?
> 
> To be fair there's a bit more information:
> 
> 20:51:22  [INFO] --- 
> tycho-eclipserun-plugin:3.0.0-SNAPSHOT:eclipse-run
> (build-.api_description) @ org.eclipse.jdt.annotation ---
> 
> 20:51:23  [INFO] Toolchain in tycho-eclipserun-plugin: 
> JDK[/opt/tools/java/openjdk/jdk-11/latest]
> 20:51:23  [INFO] Expected eclipse log file: 
> /home/jenkins/agent/workspace/eclipse.jdt.core-Github_PR-28/org.eclips
> e.jdt.annotation/target/apigeneration-workspace/data/.metadata/.log
> 
> 20:51:23  [INFO] Command line:
> 20:51:23      [/opt/tools/java/openjdk/jdk-11/latest/bin/java, -jar, 
> /home/jenkins/agent/workspace/eclipse.jdt.core-Github_PR-28/.m2/reposi
> tory/p2/osgi/bundle/org.eclipse.equinox.launcher/1.6.400.v20210924-064
> 1/org.eclipse.equinox.launcher-1.6.400.v20210924-0641.jar,
> -install,
> /home/jenkins/agent/workspace/eclipse.jdt.core-Github_PR-28/org.eclips
> e.jdt.annotation/target/apigeneration-workspace,
> -configuration,
> /home/jenkins/agent/workspace/eclipse.jdt.core-Github_PR-28/org.eclips
> e.jdt.annotation/target/apigeneration-workspace/configuration,
> -data,
> /home/jenkins/agent/workspace/eclipse.jdt.core-Github_PR-28/org.eclips
> e.jdt.annotation/target/apigeneration-workspace/data]
> 
> 
> 20:51:25  An error has occurred. See the log file
> 20:51:25
> /home/jenkins/agent/workspace/eclipse.jdt.core-Github_PR-28/org.eclipse.jdt.annotation/target/apigeneration-workspace/configuration/1650567083880.log. 
> 
> 
> Is "eclipse-run (build-.api_description)" trying to run API tools, or who is that??
> 
> So far an unknown tool has produced an unspecified error causing the 
> build to fail and wipe all traces of what happened. Not nice.
> 
> I may have to wait until the infra is more stable ...
> 
> Stephan
> 
> PS: Could jenkins give a little more information what a given build is about? 
> Just showing the unclickable text "Pull Request PR-28" looks like a 
> thing from before the invention of hypertext.
> Interestingly, "Changes" only shows new commits on master, not new 
> commits on the branch.
> _______________________________________________
> jdt-dev mailing list
> jdt-dev@xxxxxxxxxxx
> To unsubscribe from this list, visit
> https://www.eclipse.org/mailman/listinfo/jdt-dev

_______________________________________________
jdt-dev mailing list
jdt-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jdt-dev