[jbosstools-issues] [JBoss JIRA] (JBIDE-25554) Fuse tests are failing on dev-platform
Nick Boldt (JIRA)
issues at jboss.org
Thu Jan 11 08:25:00 EST 2018
[ https://issues.jboss.org/browse/JBIDE-25554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13513456#comment-13513456 ]
Nick Boldt commented on JBIDE-25554:
------------------------------------
Failure appears to be caused by the slave crashing / shutting down before the job could complete.
{code}
14:19:53 FATAL: channel is already closed
14:19:53 Command close created at
14:19:53 at hudson.remoting.Command.<init>(Command.java:60)
14:19:53 at hudson.remoting.Channel$CloseCommand.<init>(Channel.java:1123)
14:19:53 at hudson.remoting.Channel$CloseCommand.<init>(Channel.java:1121)
14:19:53 at hudson.remoting.Channel.close(Channel.java:1281)
14:19:53 at hudson.remoting.Channel.close(Channel.java:1263)
14:19:53 at hudson.remoting.Channel$CloseCommand.execute(Channel.java:1128)
14:19:53 Caused: hudson.remoting.Channel$OrderlyShutdown
14:19:53 at hudson.remoting.Channel$CloseCommand.execute(Channel.java:1129)
14:19:53 at hudson.remoting.Channel$1.handle(Channel.java:527)
14:19:53 at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:83)
14:19:53 Caused: hudson.remoting.ChannelClosedException: channel is already closed
14:19:53 at hudson.remoting.Channel.send(Channel.java:605)
14:19:53 at hudson.remoting.Request.call(Request.java:130)
14:19:53 at hudson.remoting.Channel.call(Channel.java:829)
14:19:53 at hudson.Launcher$RemoteLauncher.launch(Launcher.java:959)
14:19:53 at hudson.Launcher$ProcStarter.start(Launcher.java:384)
14:19:53 at hudson.Launcher$ProcStarter.join(Launcher.java:395)
14:19:53 at hudson.plugins.xvnc.Xvnc$DisposerImpl.tearDown(Xvnc.java:234)
14:19:53 at jenkins.tasks.SimpleBuildWrapper$EnvironmentWrapper.tearDown(SimpleBuildWrapper.java:175)
14:19:53 at hudson.model.Build$BuildExecution.doRun(Build.java:174)
14:19:53 at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:490)
14:19:53 at hudson.model.Run.execute(Run.java:1735)
14:19:53 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
14:19:53 at hudson.model.ResourceController.execute(ResourceController.java:97)
14:19:53 at hudson.model.Executor.run(Executor.java:405)
14:19:53 ERROR: Step ‘Archive the artifacts’ failed: no workspace for jbosstools-fuse_PullRequest #303
14:19:53 ERROR: Step ‘Publish JUnit test result report’ failed: no workspace for jbosstools-fuse_PullRequest #303{code}
Yet you had a good build on Dec 19 [1] of a PR request [2], as seen here [3].
[1] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstudio/view/jbosstools-fuse/job/jbosstools-fuse_PullRequest/229/
[2] https://github.com/jbosstools/jbosstools-fuse/pull/1133
[3] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstudio/view/jbosstools-fuse/job/jbosstools-fuse_PullRequest/buildTimeTrend
So... maybe this is a problem with the rhel7-devstudio-releng-16gb-ram [4] slaves?
[4] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/label/rhel7-devstudio-releng-16gb-ram/
Assuming it's not (because the slaves work for fuse builds), I've made some tweaks to the fuse PR builder job to make it more consistent with the fuse job.
https://github.com/jbdevstudio/jbdevstudio-ci/commit/2383acb8a17b4acbbc357d1b57f4f219e2a72f97
Question:
What does this variable do?
{code}FUSE_REPO_CLEANER_DELETELASTUPDATED=true{code}
I see it being set for the fuse PR job, but not the fuse job. Is that correct?
> Fuse tests are failing on dev-platform
> --------------------------------------
>
> Key: JBIDE-25554
> URL: https://issues.jboss.org/browse/JBIDE-25554
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, fusetools
> Affects Versions: 4.5.2.AM2
> Reporter: Andrej Podhradsky
> Fix For: 4.5.x
>
> Attachments: log.txt
>
>
> The job jbosstools-fuse_PullRequest is failing on dev-platform but it passes on fusesource. See the attached log file.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
More information about the jbosstools-issues
mailing list