| Summary: | Build fails in Jenkins -- but recorded as success in Gerrit | ||
|---|---|---|---|
| Product: | Community | Reporter: | Jan-Philipp Steghöfer <ec> |
| Component: | CI-Jenkins | Assignee: | CI Admin Inbox <ci.admin-inbox> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | frederic.gurr, webmaster |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Mac OS X | ||
| Whiteboard: | |||
| Bug Depends on: | |||
| Bug Blocks: | 570140 | ||
|
Description
Jan-Philipp Steghöfer
Both instances (ci.eclipse.org/capra and ci-staging.eclipse.org/capra) are triggered on Gerrit reviews. The build on ci-staging failed, because XVnc was not found. I've changed the build to run on the centos-7 image. To fix this issue for good, please take a look at bug 570140 and help to finish the migration of the Capra Jenkins instance to the new infrastructure. The build on ci-staging.eclipse.org/capra did finish successfully, but did not report on the Gerrit review. In the Jenkins log I can see the following error: https://ci-staging.eclipse.org/capra/job/build-gerrit-trigger/589/ : SUCCESS' --verified 1 --code-review 0 com.sonymobile.tools.gerrit.gerritevents.ssh.SshException: error: fatal: Applying label "Verified": 1 is restricted fatal: one or more reviews failed; review output above (1) at com.sonymobile.tools.gerrit.gerritevents.ssh.SshConnectionImpl.executeCommand(SshconnectionImpl.java:273) at com.sonymobile.tools.gerrit.gerritevents.workers.cmd.AbstractSendCommandJob.sendCommand2(AbstractSendCommandJob.java:116) Caused: java.io.IOException: Error during sending command [...] I'll investigate. Thanks for pointing me to the other bug. I will have a look as soon as ci-staging is up again. I get an "Application is not available" at the moment. We are on it, see also: https://www.eclipsestatus.io/ The cluster is now operational. -M. Any progress on getting the build bot to report back to Gerrit? Not yet, but it's on my list. I have found a temporary workaround for now. Please try again. We'll try to figure out a permanent solution. |