Community
Participate
Working Groups
hi. the performance of the run/job https://ci.eclipse.org/xtext/job/xtext-core/job/master/416/console is terribly slow. could you lease check if there is something broken? thanks Christian
Which part is slow? I need some numbers or tasks.
15:35:25 > Task :org.eclipse.xtext.tests:generateTestXtext 15:40:47 > Task :org.eclipse.xtext.tests:compileTestJava vs on a good run 13:59:41 > Task :org.eclipse.xtext.tests:generateTestXtext 14:00:19 > Task :org.eclipse.xtext.tests:compileTestJava similar performance drops through other parts of the gradle build e.g. 15:12:50 > Task :org.eclipse.xtext:compileJava 15:12:50 Note: Some input files use or override a deprecated API. 15:12:50 Note: Recompile with -Xlint:deprecation for details. 15:12:50 Note: /home/jenkins/agent/workspace/xtext-core_master/org.eclipse.xtext/xtend-gen/org/eclipse/xtext/generator/trace/node/TracedAccessorsProcessor.java uses unchecked or unsafe operations. 15:12:50 Note: Recompile with -Xlint:unchecked for details. 15:19:41 15:19:41 > Task :org.eclipse.xtext:processResources vs 13:55:37 > Task :org.eclipse.xtext:compileJava 13:55:37 Note: Some input files use or override a deprecated API. 13:55:37 Note: Recompile with -Xlint:deprecation for details. 13:55:37 Note: /home/jenkins/agent/workspace/xtext-core_master/org.eclipse.xtext/xtend-gen/org/eclipse/xtext/generator/trace/node/TracedAccessorsProcessor.java uses unchecked or unsafe operations. 13:55:37 Note: Recompile with -Xlint:unchecked for details. 13:55:40 13:55:40 > Task :org.eclipse.xtext:processResources
https://ci.eclipse.org/xtext/job/xtext-core/job/master/418/ took 25 minutes, which seems to be par for the course. 419 is now running on one of the fastest nodes we have. Could simply have been a combination of lots of simultaneous builds + yours happened to run on the slowest node + that slowest node was really busy.
problem is there again: https://ci.eclipse.org/xtext/job/xtext-core/job/release_2.22.0/3/console any idea how to avoid this. this makes it basically impossible to build a release milestone without spending 20 hours
I'll duplicate this to bug 563645 *** This bug has been marked as a duplicate of bug 563645 ***