Hi guys! When I try to run tests from Jenkins, (sometimes) I get the following info:
chrome-vnc_1 | Failed to read: session.appsFile chrome-vnc_1 | Setting default value chrome-vnc_1 | Failed to read: session.tabsAttachArea chrome-vnc_1 | Setting default value chrome-vnc_1 | Failed to read: session.cacheLife chrome-vnc_1 | Setting default value chrome-vnc_1 | Failed to read: session.cacheMax chrome-vnc_1 | Setting default value chrome-vnc_1 | Failed to read: session.autoRaiseDelay chrome-vnc_1 | Setting default value chrome-vnc_1 | Failed to read: session.screen0.opaqueMove chrome-vnc_1 | Setting default value chrome-vnc_1 | Failed to read: session.screen0.fullMaximization chrome-vnc_1 | Setting default value chrome-vnc_1 | Failed to read: session.screen0.maxIgnoreIncrement chrome-vnc_1 | Setting default value chrome-vnc_1 | Failed to read: session.screen0.maxDisableMove chrome-vnc_1 | Setting default value chrome-vnc_1 | Failed to read: session.screen0.maxDisableResize chrome-vnc_1 | Setting default value chrome-vnc_1 | Failed to read: session.screen0.workspacewarping chrome-vnc_1 | Setting default value chrome-vnc_1 | Failed to read: session.screen0.showwindowposition chrome-vnc_1 | Setting default value chrome-vnc_1 | Failed to read: session.screen0.autoRaise chrome-vnc_1 | Setting default value chrome-vnc_1 | Failed to read: session.screen0.clickRaises chrome-vnc_1 | Setting default value chrome-vnc_1 | Failed to read: session.screen0.defaultDeco chrome-vnc_1 | Setting default value chrome-vnc_1 | Failed to read: session.screen0.tab.placement chrome-vnc_1 | Setting default value chrome-vnc_1 | Failed to read: session.screen0.windowMenu chrome-vnc_1 | Setting default value chrome-vnc_1 | Failed to read: session.screen0.noFocusWhileTypingDelay chrome-vnc_1 | Setting default value chrome-vnc_1 | Failed to read: session.screen0.workspaces chrome-vnc_1 | Setting default value chrome-vnc_1 | Failed to read: session.screen0.edgeSnapThreshold chrome-vnc_1 | Setting default value chrome-vnc_1 | Failed to read: session.screen0.window.focus.alpha chrome-vnc_1 | Setting default value chrome-vnc_1 | Failed to read: session.screen0.window.unfocus.alpha chrome-vnc_1 | Setting default value chrome-vnc_1 | Failed to read: session.screen0.menu.alpha chrome-vnc_1 | Setting default value chrome-vnc_1 | Failed to read: session.screen0.menuDelay chrome-vnc_1 | Setting default value chrome-vnc_1 | Failed to read: session.screen0.tab.width chrome-vnc_1 | Setting default value chrome-vnc_1 | Failed to read: session.screen0.tooltipDelay chrome-vnc_1 | Setting default value chrome-vnc_1 | Failed to read: session.screen0.allowRemoteActions chrome-vnc_1 | Setting default value chrome-vnc_1 | Failed to read: session.screen0.clientMenu.usePixmap chrome-vnc_1 | Setting default value chrome-vnc_1 | Failed to read: session.screen0.tabs.usePixmap chrome-vnc_1 | Setting default value chrome-vnc_1 | Failed to read: session.screen0.tabs.maxOver chrome-vnc_1 | Setting default value chrome-vnc_1 | Failed to read: session.screen0.tabs.intitlebar chrome-vnc_1 | Setting default value chrome-vnc_1 | Failed to read: session.screen0.focusModel chrome-vnc_1 | Setting default value chrome-vnc_1 | Failed to read: session.screen0.tabFocusModel chrome-vnc_1 | Setting default value chrome-vnc_1 | Failed to read: session.screen0.focusNewWindows chrome-vnc_1 | Setting default value chrome-vnc_1 | Failed to read: session.screen0.focusSameHead chrome-vnc_1 | Setting default value chrome-vnc_1 | Failed to read: session.screen0.rowPlacementDirection chrome-vnc_1 | Setting default value chrome-vnc_1 | Failed to read: session.screen0.colPlacementDirection chrome-vnc_1 | Setting default value chrome-vnc_1 | Failed to read: session.screen0.windowPlacement chrome-vnc_1 | Setting default value chrome-vnc_1 | 30/08/2017 07:05:48 X DAMAGE available on display, using it for polling hints. chrome-vnc_1 | 30/08/2017 07:05:48 To disable this behavior use: '-noxdamage' chrome-vnc_1 | 30/08/2017 07:05:48 chrome-vnc_1 | 30/08/2017 07:05:48 Most compositing window managers like 'compiz' or 'beryl' chrome-vnc_1 | 30/08/2017 07:05:48 cause X DAMAGE to fail, and so you may not see any screen chrome-vnc_1 | 30/08/2017 07:05:48 updates via VNC. Either disable 'compiz' (recommended) or chrome-vnc_1 | 30/08/2017 07:05:48 supply the x11vnc '-noxdamage' command line option. chrome-vnc_1 | 30/08/2017 07:05:48 chrome-vnc_1 | 30/08/2017 07:05:48 Wireframing: -wireframe mode is in effect for window moves. chrome-vnc_1 | 30/08/2017 07:05:48 If this yields undesired behavior (poor response, painting chrome-vnc_1 | 30/08/2017 07:05:48 errors, etc) it may be disabled: chrome-vnc_1 | 30/08/2017 07:05:48 - use '-nowf' to disable wireframing completely. chrome-vnc_1 | 30/08/2017 07:05:48 - use '-nowcr' to disable the Copy Rectangle after the chrome-vnc_1 | 30/08/2017 07:05:48 moved window is released in the new position. chrome-vnc_1 | 30/08/2017 07:05:48 Also see the -help entry for tuning parameters. chrome-vnc_1 | 30/08/2017 07:05:48 You can press 3 Alt_L's (Left "Alt" key) in a row to chrome-vnc_1 | 30/08/2017 07:05:48 repaint the screen, also see the -fixscreen option for chrome-vnc_1 | 30/08/2017 07:05:48 periodic repaints. chrome-vnc_1 | 30/08/2017 07:05:48 chrome-vnc_1 | 30/08/2017 07:05:48 XFIXES available on display, resetting cursor mode chrome-vnc_1 | 30/08/2017 07:05:48 to: '-cursor most'. chrome-vnc_1 | 30/08/2017 07:05:48 to disable this behavior use: '-cursor arrow' chrome-vnc_1 | 30/08/2017 07:05:48 or '-noxfixes'. chrome-vnc_1 | 30/08/2017 07:05:48 using XFIXES for cursor drawing. chrome-vnc_1 | 30/08/2017 07:05:48 GrabServer control via XTEST. chrome-vnc_1 | 30/08/2017 07:05:48 chrome-vnc_1 | 30/08/2017 07:05:48 Scroll Detection: -scrollcopyrect mode is in effect to chrome-vnc_1 | 30/08/2017 07:05:48 use RECORD extension to try to detect scrolling windows chrome-vnc_1 | 30/08/2017 07:05:48 (induced by either user keystroke or mouse input). chrome-vnc_1 | 30/08/2017 07:05:48 If this yields undesired behavior (poor response, painting chrome-vnc_1 | 30/08/2017 07:05:48 errors, etc) it may be disabled via: '-noscr' chrome-vnc_1 | 30/08/2017 07:05:48 Also see the -help entry for tuning parameters. chrome-vnc_1 | 30/08/2017 07:05:48 You can press 3 Alt_L's (Left "Alt" key) in a row to chrome-vnc_1 | 30/08/2017 07:05:48 repaint the screen, also see the -fixscreen option for chrome-vnc_1 | 30/08/2017 07:05:48 periodic repaints. chrome-vnc_1 | 30/08/2017 07:05:48 chrome-vnc_1 | 30/08/2017 07:05:48 XKEYBOARD: number of keysyms per keycode 7 is greater chrome-vnc_1 | 30/08/2017 07:05:48 than 4 and 51 keysyms are mapped above 4. chrome-vnc_1 | 30/08/2017 07:05:48 Automatically switching to -xkb mode. chrome-vnc_1 | 30/08/2017 07:05:48 If this makes the key mapping worse you can chrome-vnc_1 | 30/08/2017 07:05:48 disable it with the "-noxkb" option. chrome-vnc_1 | 30/08/2017 07:05:48 Also, remember "-remap DEAD" for accenting characters. chrome-vnc_1 | 30/08/2017 07:05:48 chrome-vnc_1 | 30/08/2017 07:05:48 X FBPM extension not supported. chrome-vnc_1 | 30/08/2017 07:05:48 X display is not capable of DPMS. chrome-vnc_1 | 30/08/2017 07:05:48 -------------------------------------------------------- chrome-vnc_1 | 30/08/2017 07:05:48 chrome-vnc_1 | 30/08/2017 07:05:48 Default visual ID: 0x21 chrome-vnc_1 | 30/08/2017 07:05:48 Read initial data from X display into framebuffer. chrome-vnc_1 | 30/08/2017 07:05:48 initialize_screen: fb_depth/fb_bpp/fb_Bpl 24/32/5440 chrome-vnc_1 | 30/08/2017 07:05:48 chrome-vnc_1 | 30/08/2017 07:05:48 X display :99.0 is 32bpp depth=24 true color chrome-vnc_1 | 30/08/2017 07:05:48 chrome-vnc_1 | 30/08/2017 07:05:48 Listening for VNC connections on TCP port 5900 chrome-vnc_1 | 30/08/2017 07:05:48 Listening for VNC connections on TCP6 port 5900 chrome-vnc_1 | 30/08/2017 07:05:48 listen6: bind: Address already in use chrome-vnc_1 | 30/08/2017 07:05:48 Not listening on IPv6 interface. chrome-vnc_1 | 30/08/2017 07:05:48 chrome-vnc_1 | 30/08/2017 07:05:48 Xinerama is present and active (e.g. multi-head). chrome-vnc_1 | 30/08/2017 07:05:48 Xinerama: number of sub-screens: 1 chrome-vnc_1 | 30/08/2017 07:05:48 Xinerama: no blackouts needed (only one sub-screen) chrome-vnc_1 | 30/08/2017 07:05:48 chrome-vnc_1 | 30/08/2017 07:05:48 fb read rate: 174 MB/sec chrome-vnc_1 | 30/08/2017 07:05:48 fast read: reset -wait ms to: 10 chrome-vnc_1 | 30/08/2017 07:05:48 fast read: reset -defer ms to: 10 chrome-vnc_1 | 30/08/2017 07:05:48 The X server says there are 10 mouse buttons. chrome-vnc_1 | 30/08/2017 07:05:48 screen setup finished. chrome-vnc_1 | 30/08/2017 07:05:48 chrome-vnc_1 | chrome-vnc_1 | The VNC desktop is: 6ac539dfc32f:0 chrome-vnc_1 | chrome-vnc_1 | ****************************************************************************** chrome-vnc_1 | Have you tried the x11vnc '-ncache' VNC client-side pixel caching feature yet? chrome-vnc_1 | chrome-vnc_1 | The scheme stores pixel data offscreen on the VNC viewer side for faster chrome-vnc_1 | retrieval. It should work with any VNC viewer. Try it by running: chrome-vnc_1 | chrome-vnc_1 | x11vnc -ncache 10 ... chrome-vnc_1 | chrome-vnc_1 | One can also add -ncache_cr for smooth 'copyrect' window motion. chrome-vnc_1 | More info: http://www.karlrunge.com/x11vnc/faq.html#faq-client-caching chrome-vnc_1 | chrome-vnc_1 | PORT=5900 chrome-vnc_1 | Failed to read: session.screen0.slit.acceptKdeDockapps chrome-vnc_1 | Setting default value chrome-vnc_1 | Failed to read: session.screen0.slit.autoHide chrome-vnc_1 | Setting default value chrome-vnc_1 | Failed to read: session.screen0.slit.maxOver chrome-vnc_1 | Setting default value chrome-vnc_1 | Failed to read: session.screen0.slit.placement chrome-vnc_1 | Setting default value chrome-vnc_1 | Failed to read: session.screen0.slit.alpha chrome-vnc_1 | Setting default value chrome-vnc_1 | Failed to read: session.screen0.slit.onhead chrome-vnc_1 | Setting default value chrome-vnc_1 | Failed to read: session.screen0.slit.layer chrome-vnc_1 | Setting default value chrome-vnc_1 | Failed to read: session.screen0.toolbar.autoHide chrome-vnc_1 | Setting default value chrome-vnc_1 | Failed to read: session.screen0.toolbar.maxOver chrome-vnc_1 | Setting default value chrome-vnc_1 | Failed to read: session.screen0.toolbar.visible chrome-vnc_1 | Setting default value chrome-vnc_1 | Failed to read: session.screen0.toolbar.alpha chrome-vnc_1 | Setting default value chrome-vnc_1 | Failed to read: session.screen0.toolbar.layer chrome-vnc_1 | Setting default value chrome-vnc_1 | Failed to read: session.screen0.toolbar.onhead chrome-vnc_1 | Setting default value chrome-vnc_1 | Failed to read: session.screen0.toolbar.placement chrome-vnc_1 | Setting default value chrome-vnc_1 | Failed to read: session.screen0.toolbar.height chrome-vnc_1 | Setting default value chrome-vnc_1 | Failed to read: session.screen0.iconbar.mode chrome-vnc_1 | Setting default value chrome-vnc_1 | Failed to read: session.screen0.iconbar.alignment chrome-vnc_1 | Setting default value chrome-vnc_1 | Failed to read: session.screen0.iconbar.iconWidth chrome-vnc_1 | Setting default value chrome-vnc_1 | Failed to read: session.screen0.iconbar.iconTextPadding chrome-vnc_1 | Setting default value chrome-vnc_1 | Failed to read: session.screen0.iconbar.usePixmap chrome-vnc_1 | Setting default value chrome-vnc_1 | 2017-08-30 07:05:48.846:INFO::main: Logging initialized @4021ms to org.seleniumhq.jetty9.util.log.StdErrLog chrome-vnc_1 | 07:05:48.899 INFO - Driver provider org.openqa.selenium.ie.InternetExplorerDriver registration is skipped: chrome-vnc_1 | registration capabilities Capabilities [{ensureCleanSession=true, browserName=internet explorer, version=, platform=WINDOWS}] does not match the current platform LINUX chrome-vnc_1 | 07:05:48.900 INFO - Driver provider org.openqa.selenium.edge.EdgeDriver registration is skipped: chrome-vnc_1 | registration capabilities Capabilities [{browserName=MicrosoftEdge, version=, platform=WINDOWS}] does not match the current platform LINUX chrome-vnc_1 | 07:05:48.900 INFO - Driver class not found: com.opera.core.systems.OperaDriver chrome-vnc_1 | 07:05:48.901 INFO - Driver provider com.opera.core.systems.OperaDriver registration is skipped: chrome-vnc_1 | Unable to create new instances on this machine. chrome-vnc_1 | 07:05:48.902 INFO - Driver class not found: com.opera.core.systems.OperaDriver chrome-vnc_1 | 07:05:48.903 INFO - Driver provider com.opera.core.systems.OperaDriver is not registered chrome-vnc_1 | 07:05:48.905 INFO - Driver provider org.openqa.selenium.safari.SafariDriver registration is skipped: chrome-vnc_1 | registration capabilities Capabilities [{browserName=safari, version=, platform=MAC}] does not match the current platform LINUX chrome-vnc_1 | 2017-08-30 07:05:48.991:INFO:osjs.Server:main: jetty-9.2.20.v20161216 chrome-vnc_1 | 2017-08-30 07:05:49.046:INFO:osjsh.ContextHandler:main: Started o.s.j.s.ServletContextHandler@441772e{/,null,AVAILABLE} chrome-vnc_1 | 2017-08-30 07:05:49.072:INFO:osjs.AbstractConnector:main: Started ServerConnector@1576a156{HTTP/1.1,[http/1.1]}{0.0.0.0:5555} chrome-vnc_1 | 2017-08-30 07:05:49.072:INFO:osjs.Server:main: Started @4247ms chrome-vnc_1 | 07:05:49.073 INFO - Selenium Grid node is up and ready to register to the hub chrome-vnc_1 | 07:05:49.098 INFO - Starting auto registration thread. Will try to register every 5000 ms. chrome-vnc_1 | 07:05:49.099 INFO - Registering the node to the hub: http://172.25.0.101:4444/grid/register chrome-vnc_1 | 07:05:49.140 INFO - The node is registered to the hub and ready to use chrome-vnc_1 | 07:05:54.347 INFO - SessionCleaner initialized with insideBrowserTimeout 100000 and clientGoneTimeout 900000 polling every 10000 ------------------------------------ chrome-vnc_1 | 30/08/2017 07:25:02 Got connection from client 88.12.23.3 chrome-vnc_1 | 30/08/2017 07:25:02 other clients: chrome-vnc_1 | 30/08/2017 07:25:02 Normal socket connection chrome-vnc_1 | 30/08/2017 07:25:02 Disabled X server key autorepeat. chrome-vnc_1 | 30/08/2017 07:25:02 to force back on run: 'xset r on' (3 times) chrome-vnc_1 | 30/08/2017 07:25:02 incr accepted_client=1 for 88.12.23.3:58891 sock=12 chrome-vnc_1 | 30/08/2017 07:25:02 Client Protocol Version 3.8 chrome-vnc_1 | 30/08/2017 07:25:02 Protocol version sent 3.8, using 3.8 chrome-vnc_1 | 30/08/2017 07:25:02 rfbProcessClientSecurityType: executing handler for type 2 chrome-vnc_1 | 30/08/2017 07:25:02 copy_tiles: allocating first_line at size 44 chrome-vnc_1 | 30/08/2017 07:25:03 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0x00000016) chrome-vnc_1 | 30/08/2017 07:25:03 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0x00000015) chrome-vnc_1 | 30/08/2017 07:25:03 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0x0000000F) chrome-vnc_1 | 30/08/2017 07:25:03 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0xFFFFFEC6) chrome-vnc_1 | 30/08/2017 07:25:03 Enabling full-color cursor updates for client 88.12.23.3 chrome-vnc_1 | 30/08/2017 07:25:03 Enabling NewFBSize protocol extension for client 88.12.23.3 chrome-vnc_1 | 30/08/2017 07:25:03 Using ZRLE encoding for client 88.12.23.3 chrome-vnc_1 | 30/08/2017 07:25:03 Pixel format for client 88.12.23.3: chrome-vnc_1 | 30/08/2017 07:25:03 8 bpp, depth 6 chrome-vnc_1 | 30/08/2017 07:25:03 true colour: max r 3 g 3 b 3, shift r 4 g 2 b 0 chrome-vnc_1 | 30/08/2017 07:25:04 client useCopyRect: 88.12.23.3 -1 chrome-vnc_1 | 30/08/2017 07:25:04 client_set_net: 88.12.23.3 0.0087 chrome-vnc_1 | 30/08/2017 07:25:04 created xdamage object: 0x20002f chrome-vnc_1 | 30/08/2017 07:25:04 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0x00000016) chrome-vnc_1 | 30/08/2017 07:25:04 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0x00000015) chrome-vnc_1 | 30/08/2017 07:25:04 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0x0000000F) chrome-vnc_1 | 30/08/2017 07:25:04 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0xFFFFFEC6) chrome-vnc_1 | 30/08/2017 07:25:04 Enabling full-color cursor updates for client 88.12.23.3 chrome-vnc_1 | 30/08/2017 07:25:04 Enabling NewFBSize protocol extension for client 88.12.23.3 chrome-vnc_1 | 30/08/2017 07:25:04 Switching from ZRLE to raw Encoding for client 88.12.23.3 chrome-vnc_1 | 30/08/2017 07:25:04 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0x00000016) chrome-vnc_1 | 30/08/2017 07:25:04 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0x00000015) chrome-vnc_1 | 30/08/2017 07:25:04 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0x0000000F) chrome-vnc_1 | 30/08/2017 07:25:04 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0xFFFFFEC6) chrome-vnc_1 | 30/08/2017 07:25:04 Enabling full-color cursor updates for client 88.12.23.3 chrome-vnc_1 | 30/08/2017 07:25:04 Enabling NewFBSize protocol extension for client 88.12.23.3 chrome-vnc_1 | 30/08/2017 07:25:04 Switching from raw to ZRLE Encoding for client 88.12.23.3 chrome-vnc_1 | 30/08/2017 07:25:04 Pixel format for client 88.12.23.3: chrome-vnc_1 | 30/08/2017 07:25:04 32 bpp, depth 24, little endian chrome-vnc_1 | 30/08/2017 07:25:04 true colour: max r 255 g 255 b 255, shift r 16 g 8 b 0 chrome-vnc_1 | 30/08/2017 07:25:04 no translation needed chrome-vnc_1 | 30/08/2017 07:25:04 client 1 network rate 182.6 KB/sec (182.6 eff KB/sec) chrome-vnc_1 | 30/08/2017 07:25:04 client 1 latency: 36.4 ms chrome-vnc_1 | 30/08/2017 07:25:04 dt1: 0.0104, dt2: 0.1068 dt3: 0.0364 bytes: 18094 chrome-vnc_1 | 30/08/2017 07:25:04 link_rate: LR_UNKNOWN - 36 ms, 182 KB/s chrome-vnc_1 | 30/08/2017 07:25:06 client_count: 0 chrome-vnc_1 | 30/08/2017 07:25:06 Restored X server key autorepeat to: 1 chrome-vnc_1 | 30/08/2017 07:25:06 Client 88.12.23.3 gone chrome-vnc_1 | 30/08/2017 07:25:06 Statistics events Transmit/ RawEquiv ( saved) chrome-vnc_1 | 30/08/2017 07:25:06 FramebufferUpdate : 8 | 0/ 0 ( 0.0%) chrome-vnc_1 | 30/08/2017 07:25:06 raw : 1 | 17692/ 17692 ( 0.0%) chrome-vnc_1 | 30/08/2017 07:25:06 ZRLE : 7 | 19467/ 6944192 ( 99.7%) chrome-vnc_1 | 30/08/2017 07:25:06 RichCursor : 3 | 2178/ 2178 ( 0.0%) chrome-vnc_1 | 30/08/2017 07:25:06 TOTALS : 19 | 39337/ 6964062 ( 99.4%) chrome-vnc_1 | 30/08/2017 07:25:06 Statistics events Received/ RawEquiv ( saved) chrome-vnc_1 | 30/08/2017 07:25:06 PointerEvent : 61 | 366/ 366 ( 0.0%) chrome-vnc_1 | 30/08/2017 07:25:06 FramebufferUpdate : 9 | 90/ 90 ( 0.0%) chrome-vnc_1 | 30/08/2017 07:25:06 SetPixelFormat : 2 | 40/ 40 ( 0.0%) chrome-vnc_1 | 30/08/2017 07:25:06 SetEncodings : 3 | 156/ 156 ( 0.0%) chrome-vnc_1 | 30/08/2017 07:25:06 TOTALS : 75 | 652/ 652 ( 0.0%) chrome-vnc_1 | 30/08/2017 07:25:06 destroyed xdamage object: 0x20002f And Jenkins doesn't run tests, why is it happening?? If I run my test from my local computer, it runs fine, the problem is when I run the tests from Jenkins. Thanks so much!!! -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/ea6fd314-962e-4ee5-b9c3-ce78ec8886fe%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
