Bug 547803

Comment 1 Vasili Gulevich 2019-05-31 05:24:33 EDT

Default Jenkins agent on ci-staging is not equipped with Xvnc. Migration wiki [1] promises the basic UI test configuration, and RCPTT's JIPP has Xvnc plugin installed.

Please either supply Xvnc with default agent configuration, or update wiki and remove Xvnc plugin.

[1] https://wiki.eclipse.org/CBI/Jenkins_Migration_FAQ

https://ci-staging.eclipse.org/rcptt/view/active/job/rcptt-all/2298/console

Started by timer
Agent default-agent-7nwk2 is provisioned from template Kubernetes Pod Template
Agent specification [Kubernetes Pod Template] (null): 
* [jnlp] eclipsecbijenkins/jenkins-agent:latest@sha256:13bbe1abbec678a31b8c6df906e6abb24689bf6e3b9f7caaadeaf2850a32d436(resourceRequestCpu: 1250m, resourceRequestMemory: 2560Mi, resourceLimitCpu: 2375m, resourceLimitMemory: 2560Mi)
yaml:
apiVersion: v1
kind: Pod
spec:
  containers:
  - name: jnlp
    volumeMounts:
    - name: settings-xml
      mountPath: /home/jenkins/.m2/settings.xml
      subPath: settings.xml
      readOnly: true
    - name: toolchains-xml
      mountPath: /home/jenkins/.m2/toolchains.xml
      subPath: toolchains.xml
      readOnly: true
  volumes:
  - name: settings-xml
    configMap:
      name: m2-dir
      items:
      - key: settings.xml
        path: settings.xml
  - name: toolchains-xml
    configMap:
      name: m2-dir
      items:
      - key: toolchains.xml
        path: toolchains.xml


Building remotely on default-agent-7nwk2 in workspace /home/jenkins/workspace/rcptt-all
No credentials specified
Cloning the remote Git repository
Cloning repository git://git.eclipse.org/gitroot/rcptt/org.eclipse.rcptt
 > /usr/bin/git init /home/jenkins/workspace/rcptt-all # timeout=10
Fetching upstream changes from git://git.eclipse.org/gitroot/rcptt/org.eclipse.rcptt
 > /usr/bin/git --version # timeout=10
 > /usr/bin/git fetch --tags --progress git://git.eclipse.org/gitroot/rcptt/org.eclipse.rcptt +refs/heads/*:refs/remotes/origin/*
 > /usr/bin/git config remote.origin.url git://git.eclipse.org/gitroot/rcptt/org.eclipse.rcptt # timeout=10
 > /usr/bin/git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10
 > /usr/bin/git config remote.origin.url git://git.eclipse.org/gitroot/rcptt/org.eclipse.rcptt # timeout=10
Fetching upstream changes from git://git.eclipse.org/gitroot/rcptt/org.eclipse.rcptt
 > /usr/bin/git fetch --tags --progress git://git.eclipse.org/gitroot/rcptt/org.eclipse.rcptt +refs/heads/*:refs/remotes/origin/*
 > /usr/bin/git rev-parse origin/master^{commit} # timeout=10
Checking out Revision 4cf7e1310caa1f283e9cdd3a2688058ce439dffd (origin/master)
 > /usr/bin/git config core.sparsecheckout # timeout=10
 > /usr/bin/git checkout -f 4cf7e1310caa1f283e9cdd3a2688058ce439dffd
Commit message: "Bug 546589: Prevent working set changes from affecting further tests"
 > /usr/bin/git rev-list --no-walk 4cf7e1310caa1f283e9cdd3a2688058ce439dffd # timeout=10
$ pkill Xvnc
$ pkill Xrealvnc
$ sh -c "rm -f /tmp/.X*-lock /tmp/.X11-unix/X*"
Starting xvnc
[rcptt-all] $ Xvnc :43 -geometry 1024x768 -depth 24 -ac -SecurityTypes none -noreset
FATAL: Cannot run program "Xvnc" (in directory "/home/jenkins/workspace/rcptt-all"): error=2, No such file or directory
java.io.IOException: error=2, No such file or directory
	at java.lang.UNIXProcess.<init>(Unknown Source)
	at java.lang.ProcessImpl.start(Unknown Source)
Also:   hudson.remoting.Channel$CallSiteStackTrace: Remote call to JNLP4-connect connection from 10.129.12.1/10.129.12.1:40154
		at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1743)
		at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:357)
		at hudson.remoting.Channel.call(Channel.java:957)
		at hudson.Launcher$RemoteLauncher.launch(Launcher.java:1059)
		at hudson.Launcher$ProcStarter.start(Launcher.java:455)
		at hudson.plugins.xvnc.Xvnc.doSetUp(Xvnc.java:130)
		at hudson.plugins.xvnc.Xvnc.setUp(Xvnc.java:96)
		at jenkins.tasks.SimpleBuildWrapper.setUp(SimpleBuildWrapper.java:146)
		at hudson.model.Build$BuildExecution.doRun(Build.java:157)
		at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504)
		at hudson.model.Run.execute(Run.java:1816)
		at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
		at hudson.model.ResourceController.execute(ResourceController.java:97)
		at hudson.model.Executor.run(Executor.java:429)
Caused: java.io.IOException: Cannot run program "Xvnc" (in directory "/home/jenkins/workspace/rcptt-all"): error=2, No such file or directory
	at java.lang.ProcessBuilder.start(Unknown Source)
	at hudson.Proc$LocalProc.<init>(Proc.java:249)
	at hudson.Proc$LocalProc.<init>(Proc.java:218)
	at hudson.Launcher$LocalLauncher.launch(Launcher.java:936)
	at hudson.Launcher$ProcStarter.start(Launcher.java:455)
	at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1313)
	at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1266)
	at hudson.remoting.UserRequest.perform(UserRequest.java:212)
	at hudson.remoting.UserRequest.perform(UserRequest.java:54)
	at hudson.remoting.Request$2.run(Request.java:369)
	at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
	at java.util.concurrent.FutureTask.run(Unknown Source)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
	at hudson.remoting.Engine$1.lambda$newThread$0(Engine.java:93)
	at hudson.remoting.Engine$1$$Lambda$3.00000000B803E6F0.run(Unknown Source)
	at java.lang.Thread.run(Unknown Source)
Recording test results
ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error?
Archiving artifacts
Sending e-mails to: aleksandr.dudayev@xored.com
Finished: FAILURE

Comment 2 Mikaël Barbero 2019-05-31 05:28:07 EDT

From the agent name in the log "default-agent-7nwk2", you're not using the agent labelled "ui-test". 

From the wiki https://wiki.eclipse.org/CBI/Jenkins_Migration_FAQ#How_do_I_run_UI-tests_on_the_new_infra.3F

"The basic UI-test pod template has the label "ui-test" that can be specified in the job configuration under "Restrict where this project can be run".

In case the ui-test image does not work for you, you can try the "migration" pod template that should be close(r) to the environment on the old infra. Please note: this should only used during the migration and be replaced with leaner docker images eventually."