Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 549906

Summary:	Terminating xvnc hangs for several minutes
Product:	Community	Reporter:	Baily Roberts <Baily.Roberts>
Component:	CI-Jenkins	Assignee:	CI Admin Inbox <ci.admin-inbox>
Status:	CLOSED NOT_ECLIPSE	QA Contact:
Severity:	normal
Priority:	P3	CC:	ed, frederic.gurr, webmaster
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Windows 10
Whiteboard:

Description Baily Roberts

2019-08-08 18:38:50 EDT

During out dev review builds( https://ci.eclipse.org/osee/job/osee_dev_review/11630/console) at the end of every successful build, the build seemingly hangs for about 5 minutes. The console output displays: 
Terminating xvnc 
With a spinning progress wheel next to it. After about 5 minutes the build will finish successfully. Is it normally supposed to take this long for every build? Is there anything we can do to speed this time up?

Comment 1 Frederic Gurr

2019-08-12 12:18:42 EDT

I was able to reproduce this behavior. It is in fact the "Terminating xvnc" part that takes a couple of minutes. The same issue has been reported before in bug 545349 comment 11.

We will look into it.

Comment 2 Baily Roberts

2019-08-21 13:49:12 EDT

We timed it and it takes xvnc 6 minutes to terminate. Have you found a way to speed up to termination process or stop it from seemingly hanging?

Comment 3 Frederic Gurr

2019-08-21 13:59:26 EDT

No, not yet.

Comment 4 Frederic Gurr

2019-08-27 17:06:00 EDT

I've narrowed the problem down to this line in the Xvnc Jenkins Plugin:
https://github.com/jenkinsci/xvnc-plugin/blob/master/src/main/java/hudson/plugins/xvnc/Xvnc.java#L240

I'll open a bug on the Jenkins bug tracker and link to it.

In the meantime you can disable the option "Create a dedicated Xauthority file per build" to save 4 minutes. During my tests it consistently took only ~2min instead of ~6min to terminate Xvnc.

Comment 5 Frederic Gurr

2019-08-28 07:50:50 EDT

(In reply to Frederic Gurr from comment #4)
> I'll open a bug on the Jenkins bug tracker and link to it.
=> https://issues.jenkins-ci.org/browse/JENKINS-59119

Comment 6 Ed Willink

2019-11-26 12:36:21 EST

The bug seems to be only MINOR at Jenkins; I thought we had some push or was that only for Hudson.

The "Create a dedicated Xauthority file per build" option has no associated explanation. It would seem that one polarity is correct. What is the consequence of not creating a dedicated Xauthority? do multiple builds interact adversely ?