Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[jdt-core-dev] All JDT core builds are currently failing

https://hudson.eclipse.org/platform/job/eclipse.jdt.core-Gerrit/

All the builds seem to be failing. Anyone know how to fix it? The last few lines of the build console look like this:

04:17:16  [WARNING] Could not transfer metadata org.eclipse:eclipse-platform-parent:4.7.0-SNAPSHOT/maven-metadata.xml from/to eclipse-hosted (https://repo.eclipse.org/content/repositories/eclipse/): Failed to transfer file: https://repo.eclipse.org/content/repositories/eclipse/org/eclipse/eclipse-platform-parent/4.7.0-SNAPSHOT/maven-metadata.xml. Return code is: 503 , ReasonPhrase:Service Unavailable.
04:17:16  Downloading: https://repo.eclipse.org/content/repositories/eclipse/org/eclipse/eclipse-platform-parent/4.7.0-SNAPSHOT/eclipse-platform-parent-4.7.0-SNAPSHOT.pom
04:18:16  [ERROR] [ERROR] Some problems were encountered while processing the POMs:
04:18:16  [FATAL] Non-resolvable parent POM for eclipse.jdt.core:eclipse.jdt.core:4.7.0-SNAPSHOT: Could not transfer artifact org.eclipse:eclipse-platform-parent:pom:4.7.0-SNAPSHOT from/to eclipse-hosted (https://repo.eclipse.org/content/repositories/eclipse/): Failed to transfer file: https://repo.eclipse.org/content/repositories/eclipse/org/eclipse/eclipse-platform-parent/4.7.0-SNAPSHOT/eclipse-platform-parent-4.7.0-SNAPSHOT.pom. Return code is: 503 , ReasonPhrase:Service Unavailable. and 'parent.relativePath' points at wrong local POM @ line 15, column 11
04:18:16   @ 
04:18:16  [INFO] o.h.m.e.h.MavenExecutionResultHandler - Build failed with exception(s)
04:18:16  [INFO] o.h.m.e.h.MavenExecutionResultHandler - [1] org.apache.maven.project.ProjectBuildingException: Some problems were encountered while processing the POMs:
04:18:16  [FATAL] Non-resolvable parent POM for eclipse.jdt.core:eclipse.jdt.core:4.7.0-SNAPSHOT: Could not transfer artifact org.eclipse:eclipse-platform-parent:pom:4.7.0-SNAPSHOT from/to eclipse-hosted (https://repo.eclipse.org/content/repositories/eclipse/): Failed to transfer file: https://repo.eclipse.org/content/repositories/eclipse/org/eclipse/eclipse-platform-parent/4.7.0-SNAPSHOT/eclipse-platform-parent-4.7.0-SNAPSHOT.pom. Return code is: 503 , ReasonPhrase:Service Unavailable. and 'parent.relativePath' points at wrong local POM @ line 15, column 11
04:18:16  
04:18:16  [DEBUG] Closing connection to remote
04:18:16  [ERROR] The build could not read 1 project -> [Help 1]
04:18:16  [ERROR]   
04:18:16  [ERROR]   The project eclipse.jdt.core:eclipse.jdt.core:4.7.0-SNAPSHOT (/jobs/genie.platform/eclipse.jdt.core-Gerrit/workspace/pom.xml) has 1 error
04:18:16  [ERROR]     Non-resolvable parent POM for eclipse.jdt.core:eclipse.jdt.core:4.7.0-SNAPSHOT: Could not transfer artifact org.eclipse:eclipse-platform-parent:pom:4.7.0-SNAPSHOT from/to eclipse-hosted (https://repo.eclipse.org/content/repositories/eclipse/): Failed to transfer file: https://repo.eclipse.org/content/repositories/eclipse/org/eclipse/eclipse-platform-parent/4.7.0-SNAPSHOT/eclipse-platform-parent-4.7.0-SNAPSHOT.pom. Return code is: 503 , ReasonPhrase:Service Unavailable. and 'parent.relativePath' points at wrong local POM @ line 15, column 11 -> [Help 2]
04:18:16  [ERROR] 
04:18:16  [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
04:18:16  [ERROR] Re-run Maven using the -X switch to enable full debug logging.
04:18:16  [ERROR] 
04:18:16  [ERROR] For more information about the errors and possible solutions, please read the following articles:
04:18:16  [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
04:18:16  [ERROR] [Help 2] http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException
04:18:18  [DEBUG] Waiting for process to finish
04:18:18  [DEBUG] Result: 1
04:18:18  Recording test results
04:18:18  Finished: FAILURE

Also, is there anything we can do to make the build machines work more reliably? Their uptime seems to be dismal. I've been fixing some of the flakey unit tests, but most of the failures seem to be caused by the infrastructure.

  - Stefan

Back to the top