centos -xvnc not working probably because its slow

Summary

(Summarize the bug encountered concisely)

Steps to reproduce

(How one can reproduce the issue - this is very important)

What is the current bug behavior?

(What actually happens)

What is the expected correct behavior?

(What you should see instead)

Relevant logs and/or screenshots

(Add a link to or paste any relevant logs - please use code blocks (```) to format console output, logs, and code, as it's very hard to read otherwise.)

See https://ci.eclipse.org/jdt/job/eclipse.jdt.core-Github/job/PR-652/3/console

Running on centos-8-3tqvn in /home/jenkins/agent/workspace/eclipse.jdt.core-Github_PR-652
[Pipeline] {
[Pipeline] stage
[Pipeline] { (Declarative: Checkout SCM)
[Pipeline] checkout
The recommended git tool is: git
using credential github-bot
Cloning the remote Git repository
Cloning with configured refspecs honoured and without tags
Cloning repository https://github.com/eclipse-jdt/eclipse.jdt.core.git
 > git init /home/jenkins/agent/workspace/eclipse.jdt.core-Github_PR-652 # timeout=10
Fetching upstream changes from https://github.com/eclipse-jdt/eclipse.jdt.core.git
 > git --version # timeout=10
 > git --version # 'git version 2.27.0'
using GIT_ASKPASS to set credentials GitHub bot (username/token)
 > git fetch --no-tags --force --progress -- https://github.com/eclipse-jdt/eclipse.jdt.core.git +refs/pull/652/head:refs/remotes/origin/PR-652 # timeout=10
Fetching without tags
Checking out Revision b1c22672ab58509856d4aab7d387eb08a7783830 (PR-652)
 > git config remote.origin.url https://github.com/eclipse-jdt/eclipse.jdt.core.git # timeout=10
 > git config --add remote.origin.fetch +refs/pull/652/head:refs/remotes/origin/PR-652 # timeout=10
 > git config remote.origin.url https://github.com/eclipse-jdt/eclipse.jdt.core.git # timeout=10
Fetching upstream changes from https://github.com/eclipse-jdt/eclipse.jdt.core.git
using GIT_ASKPASS to set credentials GitHub bot (username/token)
 > git fetch --no-tags --force --progress -- https://github.com/eclipse-jdt/eclipse.jdt.core.git +refs/pull/652/head:refs/remotes/origin/PR-652 # timeout=10
 > git config core.sparsecheckout # timeout=10
 > git checkout -f b1c22672ab58509856d4aab7d387eb08a7783830 # timeout=10
Commit message: "Issue 647 - https://github.com/eclipse-jdt/eclipse.jdt.core/issues/647 - Local variable referenced from guard not effectively final"
 > git rev-list --no-walk b1c22672ab58509856d4aab7d387eb08a7783830 # timeout=10
[Pipeline] }
[Pipeline] // stage
[Pipeline] withEnv
[Pipeline] {
[Pipeline] timeout
Timeout set to expire in 1 hr 30 min
[Pipeline] {
[Pipeline] timestamps
[Pipeline] {
[Pipeline] stage
[Pipeline] { (Declarative: Tool Install)
[Pipeline] tool
[Pipeline] envVarsForTool
[Pipeline] tool
[Pipeline] envVarsForTool
[Pipeline] }
[Pipeline] // stage
[Pipeline] withEnv
[Pipeline] {
[Pipeline] stage
[Pipeline] { (Build)
[Pipeline] tool
[Pipeline] envVarsForTool
[Pipeline] tool
[Pipeline] envVarsForTool
[Pipeline] withEnv
[Pipeline] {
[Pipeline] xvnc
12:15:31  $ pkill Xvnc
12:15:31  $ pkill Xrealvnc
12:15:31  $ sh -c "rm -f /tmp/.X*-lock /tmp/.X11-unix/X*"
Cancelling nested steps due to timeout
[Pipeline] // xvnc
Post stage
[Pipeline] archiveArtifacts
13:45:14  Archiving artifacts
[Pipeline] recordIssues
13:45:25  [AcuCobol] Sleeping for 5 seconds due to JENKINS-32191...
13:45:30  [AcuCobol] Parsing console log (workspace: '/home/jenkins/agent/workspace/eclipse.jdt.core-Github_PR-652')
13:45:32  [AcuCobol] -> found 0 issues (skipped 0 duplicates)
13:45:32  [AcuCobol] Parsing console log (workspace: '/home/jenkins/agent/workspace/eclipse.jdt.core-Github_PR-652')
13:45:32  [AcuCobol] -> found 0 issues (skipped 0 duplicates)
13:45:32  [AcuCobol] Successfully parsed console log
13:45:32  [AcuCobol] -> found 0 issues (skipped 0 duplicates)
13:45:32  [AcuCobol] Parsing console log (workspace: '/home/jenkins/agent/workspace/eclipse.jdt.core-Github_PR-652')
13:45:32  [AcuCobol] Skipping post processing
13:45:32  [AcuCobol] No filter has been set, publishing all 0 issues
13:45:32  [AcuCobol] Repository miner is not configured, skipping repository mining
13:45:32  [AcuCobol] Reference build recorder is not configured
13:45:32  [AcuCobol] Obtaining reference build from same job (PR-652)
13:45:32  [AcuCobol] No valid reference build found that meets the criteria (NO_JOB_FAILURE - SUCCESSFUL_QUALITY_GATE)
13:45:32  [AcuCobol] All reported issues will be considered outstanding
13:45:32  [AcuCobol] Evaluating quality gates
13:45:32  [AcuCobol] -> PASSED - Delta (any severity): 0 - Quality Gate: 1
13:45:32  [AcuCobol] -> All quality gates have been passed
13:45:32  [AcuCobol] Health report is disabled - skipping
13:45:32  [AcuCobol] Created analysis result for 0 issues (found 0 new issues, fixed 0 issues)
13:45:32  [AcuCobol] Attaching ResultAction with ID 'acu-cobol' to build 'eclipse.jdt.core-Github/PR-652 #3'.
Body did not finish within grace period; terminating with extreme prejudice
Error when executing always post condition:
org.jenkinsci.plugins.workflow.steps.FlowInterruptedException
	at org.jenkinsci.plugins.workflow.steps.TimeoutStepExecution.cancel(TimeoutStepExecution.java:168)
	at jenkins.security.ImpersonatingScheduledExecutorService$1.run(ImpersonatingScheduledExecutorService.java:67)
	at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
	at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
	at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
	at java.base/java.lang.Thread.run(Thread.java:840)

[Pipeline] }
[Pipeline] // withEnv
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
[Pipeline] // withEnv
[Pipeline] }
[Pipeline] // timestamps
[Pipeline] }
[Pipeline] // timeout
[Pipeline] }
[Pipeline] // withEnv
[Pipeline] }
[Pipeline] // node
[Pipeline] End of Pipeline
Timeout has been exceeded

GitHub has been notified of this commit’s build result

Finished: ABORTED

Priority

• Urgent
• High
• Medium
• Low

Severity

• Blocker
• Major
• Normal
• Low

Impact

(What is the impact of this issue? Is it blocking a release? Are there any time constraints?, for example: "We have a release tomorrow") JDT.Core tests were not running