Skip to content
Snippets Groups Projects

CI: E2E tests are not working since docker image update

    • Closed Issue created by David Dorchies @david.dorchies

    Example in https://forgemia.inra.fr/cassiopee/nghyd/-/jobs/808720#L75 :

    Execution of 61 workers started at 2024-01-11T07:54:53.198Z
[0-0] RUNNING in chrome - file:///e2e/app.e2e-spec.ts
[0-0] Error in "ngHyd − start page when app starts, user should be redirected to /list page"
    at <Jasmine>
    at listOnTimeout (node:internal/timers:569:17)
    at processTimers (node:internal/timers:512:7)
[0-0] 2024-01-11T07:56:55.093Z WARN webdriver: Request timed out! Consider increasing the "connectionRetryTimeout" option.
[0-0] 2024-01-11T07:57:07.136Z ERROR webdriver: Request failed with status 404 due to invalid session id: invalid session id
[0-0] Jasmine received a result after the suite finished:
[0-0] {
[0-0]   matcherName: '',
[0-0]   message: 'invalid session id: invalid session id',
[0-0]   stack: 'invalid session id: invalid session id\n' +
[0-0]     '    at processTicksAndRejections (node:internal/process/task_queues:95:5)',
[0-0]   passed: false,
[0-0]   expected: '',
[0-0]   actual: ''
[0-0] }
[0-0] FAILED in chrome - file:///e2e/app.e2e-spec.ts

    Designs

      Child items ...

      2. Activity

      • David Dorchies changed milestone to %4.18.0

        changed milestone to %4.18.0

      • David Dorchies added Internal bug critical labels

        added Internal bug critical labels

      • David Dorchies assigned to @david.dorchies

        assigned to @david.dorchies

      • David Dorchies added Doing label

        added Doing label

      • David Dorchies created branch 648-ci-e2e-tests-are-not-working-since-docker-image-update to address this issue

        created branch 648-ci-e2e-tests-are-not-working-since-docker-image-update to address this issue

      • David Dorchies mentioned in merge request !243 (merged)

        mentioned in merge request !243 (merged)

      • David Dorchies mentioned in commit cb9edb31

        mentioned in commit cb9edb31

      • David Dorchies mentioned in commit 4622b47f

        mentioned in commit 4622b47f

      • David Dorchies
        David Dorchies @david.dorchies ·
        Author Owner

        Adding trace with:

            logLevel: 'trace',
    logLevels: {
        webdriver: 'trace',
        '@wdio/jasmine-framework': 'trace'
    },

        I got this error at chrome execution:

        2024-01-11T13:45:02.512Z WARN chromedriver: [1704980702.502][INFO]: Launching chrome: /usr/bin/chromium --allow-pre-commit-input --disable-background-networking --disable-client-side-phishing-detection --disable-default-apps --disable-dev-shm-usage --disable-hang-monitor --disable-popup-blocking --disable-prompt-on-repost --disable-setuid-sandbox --disable-sync --enable-automation --enable-logging --headless --ignore-certificate-errors --log-level=0 --no-first-run --no-sandbox --no-service-autorun --password-store=basic --remote-debugging-port=0 --test-type=webdriver --use-mock-keychain --user-data-dir=/tmp/.org.chromium.Chromium.JLu5YW data:,
2024-01-11T13:45:04.843Z WARN chromedriver: [0111/134504.841830:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
2024-01-11T13:45:05.386Z WARN chromedriver: [0111/134505.385901:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
2024-01-11T13:45:05.386Z WARN chromedriver: [0111/134505.386063:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
2024-01-11T13:45:05.526Z WARN chromedriver: [0111/134505.525947:ERROR:angle_platform_impl.cc(44)] Display.cpp:1052 (initialize): ANGLE Display::initialize error 12289: Could not open the default X display.
2024-01-11T13:45:05.527Z WARN chromedriver: ERR: Display.cpp:1052 (initialize): ANGLE Display::initialize error 12289: Could not open the default X display.
2024-01-11T13:45:05.527Z WARN chromedriver: [0111/134505.526434:ERROR:gl_display.cc(515)] EGL Driver message (Critical) eglInitialize: Could not open the default X display.
2024-01-11T13:45:05.527Z WARN chromedriver: [0111/134505.526609:ERROR:gl_display.cc(786)] eglInitialize Default failed with error EGL_NOT_INITIALIZED
2024-01-11T13:45:05.529Z WARN chromedriver: [0111/134505.527885:ERROR:gl_display.cc(820)] Initialization of all EGL display types failed.
2024-01-11T13:45:05.529Z WARN chromedriver: [0111/134505.529290:ERROR:gl_ozone_egl.cc(26)] GLDisplayEGL::Initialize failed.
2024-01-11T13:45:05.530Z WARN chromedriver: [0111/134505.529852:ERROR:angle_platform_impl.cc(44)] Display.cpp:1052 (initialize): ANGLE Display::initialize error 12289: Could not open the default X display.
2024-01-11T13:45:05.530Z WARN chromedriver: ERR: Display.cpp:1052 (initialize): ANGLE Display::initialize error 12289: Could not open the default X display.
2024-01-11T13:45:05.530Z WARN chromedriver: [0111/134505.530155:ERROR:gl_display.cc(515)] EGL Driver message (Critical) eglInitialize: Could not open the default X display.
2024-01-11T13:45:05.530Z WARN chromedriver: [0111/134505.530275:ERROR:gl_display.cc(786)] eglInitialize Default failed with error EGL_NOT_INITIALIZED
2024-01-11T13:45:05.531Z WARN chromedriver: [0111/134505.530543:ERROR:gl_display.cc(820)] Initialization of all EGL display types failed.
2024-01-11T13:45:05.531Z WARN chromedriver: [0111/134505.530755:ERROR:gl_ozone_egl.cc(26)] GLDisplayEGL::Initialize failed.
2024-01-11T13:45:05.535Z WARN chromedriver: [0111/134505.535058:ERROR:viz_main_impl.cc(196)] Exiting GPU process due to errors during initialization

        The log Could not open the default X display is usually solved by adding --headless in chrome launch arguments but it's already there...

        Try to add --no-gpu on chrome launch arguments to solve this...

        Edited by David Dorchies
      • David Dorchies mentioned in commit b3338463

        mentioned in commit b3338463

      • David Dorchies mentioned in commit fedc1595

        mentioned in commit fedc1595

      • David Dorchies mentioned in commit 80d2bd5c

        mentioned in commit 80d2bd5c

      • David Dorchies mentioned in commit d766d16d

        mentioned in commit d766d16d

        • David Dorchies
          David Dorchies @david.dorchies ·
          Author Owner

          By using default wdio configuration for managing chrome and chromedriver, I get this result:

          Execution of 52 workers started at 2024-01-11T15:31:01.652Z
2024-01-11T15:31:01.667Z INFO @wdio/cli:launcher: Run onPrepare hook
2024-01-11T15:31:01.670Z INFO @wdio/cli:launcher: Run onWorkerStart hook
2024-01-11T15:31:01.671Z INFO @wdio/local-runner: Start worker 0-0 with arg: run,./wdio.conf.ts
2024-01-11T15:31:01.686Z DEBUG @wdio/local-runner: Send command run to worker with cid "0-0"
[0-0] 2024-01-11T15:31:02.691Z INFO @wdio/local-runner: Run worker command: run
[0-0] 2024-01-11T15:31:02.877Z DEBUG @wdio/runner: init remote session
[0-0] RUNNING in chrome - file:///e2e/app.e2e-spec.ts
[0-0] 2024-01-11T15:31:02.980Z DEBUG @wdio/runner: init remote session
[0-0] 2024-01-11T15:31:02.990Z INFO devtools:puppeteer: Initiate new session using the DevTools protocol
[0-0] 2024-01-11T15:31:02.992Z INFO devtools: Launch Google Chrome (undefined) with flags: --enable-automation --disable-popup-blocking --disable-extensions --disable-background-networking --disable-background-timer-throttling --disable-backgrounding-occluded-windows --disable-sync --metrics-recording-only --disable-default-apps --mute-audio --no-first-run --no-default-browser-check --disable-hang-monitor --disable-prompt-on-repost --disable-client-side-phishing-detection --password-store=basic --use-mock-keychain --disable-component-extensions-with-background-pages --disable-breakpad --disable-dev-shm-usage --disable-ipc-flooding-protection --disable-renderer-backgrounding --force-fieldtrials=*BackgroundTracing/default/ --enable-features=NetworkService,NetworkServiceInProcess --disable-features=site-per-process,TranslateUI,BlinkGenPropertyTrees --window-position=0,0 --window-size=1200,900 --headless --no-sandbox --disable-setuid-sandbox --disable-dev-shm-usage
[0-0] 2024-01-11T15:31:03.577Z INFO devtools: Connect Puppeteer with browser on port 42743
[0-0] 2024-01-11T15:31:03.663Z DEBUG @wdio/utils:shim: Finished to run "beforeHook" hook in 0ms
[0-0] 2024-01-11T15:31:03.664Z DEBUG @wdio/utils:shim: Finished to run "afterHook" hook in 0ms
[0-0] 2024-01-11T15:31:03.674Z INFO devtools: COMMAND navigateTo("http://localhost:4200/")
[0-0] Error in "ngHyd − start page when app starts, user should be redirected to /list page"
    at <Jasmine>
    at listOnTimeout (node:internal/timers:569:17)
    at processTimers (node:internal/timers:512:7)
[0-0] 2024-01-11T15:33:14.481Z INFO devtools: RESULT null
[0-0] 2024-01-11T15:33:14.487Z INFO devtools: COMMAND deleteSession()
[0-0] 2024-01-11T15:33:14.495Z INFO devtools: RESULT null
[0-0] Jasmine received a result after the suite finished:
[0-0] {
[0-0]   matcherName: '',
[0-0]   message: "Error: Couldn't find page handle",
[0-0]   stack: '    at DevToolsDriver.getPageHandle (file:///builds/cassiopee/nghyd/node_modules/devtools/build/devtoolsdriver.js:199:19)\n' +
[0-0]     '    at DevToolsDriver.checkPendingNavigations (file:///builds/cassiopee/nghyd/node_modules/devtools/build/devtoolsdriver.js:208:25)\n' +
[0-0]     '    at DevToolsDriver.checkPendingNavigations (file:///builds/cassiopee/nghyd/node_modules/devtools/build/devtoolsdriver.js:254:20)\n' +
[0-0]     '    at async Browser.wrappedCommand (file:///builds/cassiopee/nghyd/node_modules/devtools/build/devtoolsdriver.js:122:13)',
[0-0]   passed: false,
[0-0]   expected: '',
[0-0]   actual: ''
[0-0] }
2024-01-11T15:33:14.621Z DEBUG @wdio/local-runner: Runner 0-0 finished with exit code 1
[0-0] FAILED in chrome - file:///e2e/app.e2e-spec.ts
2024-01-11T15:33:14.622Z INFO @wdio/cli:launcher: Run onWorkerEnd hook
        • David Dorchies
          David Dorchies @david.dorchies ·
          Author Owner

          No more issues with chromedriver but there is now this new error Error: Couldn't find page handle.

        • Please register or sign in to reply
      • David Dorchies mentioned in commit 049173c7

        mentioned in commit 049173c7

      • David Dorchies mentioned in commit c0c60480

        mentioned in commit c0c60480

      • David Dorchies mentioned in commit 2354736c

        mentioned in commit 2354736c

      • David Dorchies closed with merge request !243 (merged)

        closed with merge request !243 (merged)

      • David Dorchies mentioned in commit db1d9a85

        mentioned in commit db1d9a85

      Please register or sign in to reply