Default screen resolution in Jenkins/Xvnc has changed and can not be modified
Summary
Since 2024-01-30, this jobs on the Sirius Jenkins has been failing. We did not change anything on our side (except asking for the addition of a new Jenkins plug-in which may have triggered some refresh/update of the base image?).
Steps to reproduce
- Trigger https://ci.eclipse.org/sirius/view/active/job/sirius.tests-master/
- Watch it fail almost immediatly (at least as soon as it gets an available runner)
What is the current bug behavior?
Our job configuration uses xrandr
to enforce a specific screen resolution for test consistency (1440x900 because... historical reasons).
Since 2024-01-30, we get this message: Size 1440x900 not found in available modes
Starting xvnc
[centos-7-6gb] $ Xvnc :78 -geometry 1024x768 -depth 24 -ac -SecurityTypes none -noreset
Xvnc TigerVNC 1.8.0 - built Jan 10 2024 16:20:34
Copyright (C) 1999-2017 TigerVNC Team and many others (see README.txt)
See http://www.tigervnc.org for information on TigerVNC.
Underlying X server release 12004000, The X.Org Foundation
Thu Feb 1 23:06:33 2024
vncext: VNC extension running!
vncext: Listening for VNC connections on all interface(s), port 5978
vncext: created VNC server for screen 0
[centos-7-6gb] $ /bin/sh -xe /tmp/jenkins1654940366849897869.sh
+ rm -rf /home/jenkins/agent/workspace/sirius.tests-master/PLATFORM/2023-03/SUITE/junit/jdk/openjdk-jdk17-latest/label/centos-7-6gb/plugins/org.eclipse.sirius.tests.swtbot/screenshots
+ xrandr -s 1440x900
Size 1440x900 not found in available modes
and then the job fails immediatly.
In the last job launched on 2024-01-29, this xrandr
invocation worked fine, and actually seemed redundant in our case becasue the default Xvnc arguments already used that:
Starting xvnc
[centos-7-6gb] $ Xvnc :79 -geometry 1440x900 -depth 16 -dpi 100 -ac -SecurityTypes none -noreset
Xvnc TigerVNC 1.8.0 - built Jan 10 2024 16:20:34
Copyright (C) 1999-2017 TigerVNC Team and many others (see README.txt)
See http://www.tigervnc.org for information on TigerVNC.
Underlying X server release 12004000, The X.Org Foundation
Mon Jan 29 23:01:23 2024
vncext: VNC extension running!
vncext: Listening for VNC connections on all interface(s), port 5979
vncext: created VNC server for screen 0
[centos-7-6gb] $ /bin/sh -xe /tmp/jenkins14640985234987035624.sh
+ rm -rf /home/jenkins/agent/workspace/sirius.tests-master/PLATFORM/2023-03/SUITE/junit/jdk/openjdk-jdk17-latest/label/centos-7-6gb/plugins/org.eclipse.sirius.tests.swtbot/screenshots
+ xrandr -s 1440x900
+ xsetroot -solid grey
+ xhost +
+ vncconfig -iconic
access control disabled, clients can connect from any host
+ sleep 2
+ sleep 2
+ metacity --replace --sm-disable --display=:79
What is the expected correct behavior?
Begin able to use xrandr
to ask for a specific resolution for our tests (and not have to audit/update hundreds or more tests to make sure they work in the new imposed 1024x768 resolution).
Priority
-
Urgent -
High -
Medium -
Low
Severity
-
Blocker -
Major -
Normal -
Low
Impact
We (Sirius Desktop) can no longer run our automated test suites on the Eclipse infra.