xvfb

How to start a wide browser inside a docker container, for Protractor testing

▼魔方 西西 提交于 2021-02-07 14:19:20
问题 When running end to end tests inside a docker container we need the browser to be wide, to make sure the elements (aButton) that are positioned far right are actually visible and test like expect(mainPage.aButton.isDisplayed()).toBeTruthy(); succeed. When displaying the browser width we always get a value close to 1050 as a maximum: browser.driver.manage().window().getSize().then(function(size) { console.log('browser size', size); }); displays: browser size { height: 748, width: 1050, class:

Java AWT requires X11 , how to use xvfb (ubuntu 14.04)

久未见 提交于 2021-01-27 21:45:47
问题 I Have a java application that requires X11 DISPLAY variable, the exception I am getting is: Caused by: java.awt.HeadlessException: No X11 DISPLAY variable was set, but this program performed an operation which requires it. at java.awt.GraphicsEnvironment.checkHeadless(GraphicsEnvironment.java:204) at java.awt.Window.<init>(Window.java:536) at java.awt.Frame.<init>(Frame.java:420) I've installed Xvfb on the ubuntu machine: root 1470 1469 0 02:40 pts/3 00:00:00 Xvfb :1 -screen 0 1152x900x8 But

Is xvfb (with Mesa 19.2) compatible with Vulkan?

天大地大妈咪最大 提交于 2021-01-27 05:31:40
问题 I'm trying to run a Vulkan-based graphical application on a headless Ubuntu 19.10 virtual machine, via xvfb. Starting from a bare Ubuntu 19.10 image (created using lxc), I prep the machine as follows: > sudo apt update > sudo apt install -y xvfb mesa-vulkan-drivers vulkan-tools I then run the following two commands: In Terminal 1: Start XVFB Xvfb :1 -screen 0 1024x768x24 In Terminal 2: Run vulkaninfo > DISPLAY=:1 vulkaninfo ========== VULKANINFO ========== Vulkan Instance Version: 1.1.114

XVFB on Jenkins connecting to wrong display. Display shows black screen

淺唱寂寞╮ 提交于 2020-11-29 21:33:07
问题 I am trying to execute headless chrome Selenium tests via Jenkins using XVFB on UBUNTU AWS/VM. My Jenkins XVFB config is: Pre-build Execute Shell: export DISPLAY=:98 x11vnc -xkb -noxrecord -noxfixes -noxdamage -display :98 -auth /var/run/lightdm/root/:0 -rfbport 5900 When build starts, I see: Xvfb starting$ /usr/bin/Xvfb :98 -screen 0 1024x768x24 -fbdir /var/lib/jenkins/xvfb-82-..fbdir10942188934689457655 [Jenkins-Headless] $ /bin/sh -xe /tmp/jenkins11502774511620101086.sh + export DISPLAY=

XVFB on Jenkins connecting to wrong display. Display shows black screen

↘锁芯ラ 提交于 2020-11-29 21:31:09
问题 I am trying to execute headless chrome Selenium tests via Jenkins using XVFB on UBUNTU AWS/VM. My Jenkins XVFB config is: Pre-build Execute Shell: export DISPLAY=:98 x11vnc -xkb -noxrecord -noxfixes -noxdamage -display :98 -auth /var/run/lightdm/root/:0 -rfbport 5900 When build starts, I see: Xvfb starting$ /usr/bin/Xvfb :98 -screen 0 1024x768x24 -fbdir /var/lib/jenkins/xvfb-82-..fbdir10942188934689457655 [Jenkins-Headless] $ /bin/sh -xe /tmp/jenkins11502774511620101086.sh + export DISPLAY=

XVFB on Jenkins connecting to wrong display. Display shows black screen

放肆的年华 提交于 2020-11-29 21:28:31
问题 I am trying to execute headless chrome Selenium tests via Jenkins using XVFB on UBUNTU AWS/VM. My Jenkins XVFB config is: Pre-build Execute Shell: export DISPLAY=:98 x11vnc -xkb -noxrecord -noxfixes -noxdamage -display :98 -auth /var/run/lightdm/root/:0 -rfbport 5900 When build starts, I see: Xvfb starting$ /usr/bin/Xvfb :98 -screen 0 1024x768x24 -fbdir /var/lib/jenkins/xvfb-82-..fbdir10942188934689457655 [Jenkins-Headless] $ /bin/sh -xe /tmp/jenkins11502774511620101086.sh + export DISPLAY=

XVFB and Selenium on EC2 - Unable to view Chrome UI on VNC Viewer

谁都会走 提交于 2020-08-26 05:38:18
问题 My Selenium headless tests are triggered from Jenkins server and run in EC2-Ubuntu. I want to view the test live on Chrome so I installed Xvfb plugin on Jenkins. On EC2 I installed Xvfb. When I start executing the build, my test starts execution and I see below logs: Xvfb /usr/bin/Xvfb :1 -fbdir /var/lib/jenkins/xvfb 27-..fbdir13700092919317283985 Parsing POMs Established TCP socket on 30810 and I see the test is running successfully. Now I do SSH to EC2 from Mac terminal by ssh -L 5901