Error while running tests from Gitlab

[shivabhardwaj18]

Hello,
I am getting following error when trying to run seleniumbase tests from Gitlab. Is anyone aware about it or has faced anything similar:

File "/usr/local/bin/seleniumbase", line 8, in <module> sys.exit(main()) File "/usr/local/lib/python3.9/site-packages/seleniumbase/console_scripts/run.py", line 773, in main sb_install.main() File "/usr/local/lib/python3.9/site-packages/seleniumbase/console_scripts/sb_install.py", line 711, in main raise Exception("Expecting only one file in %s!" % zip_file_path) Exception: Expecting only one file in /usr/local/lib/python3.9/site-packages/seleniumbase/drivers/chromedriver_linux64.zip! Cleaning up file based variables ERROR: Job failed: command terminated with exit code 1

My yml file looks like below:

`

variables:
  ENVIRONMENT: "pp"
  
stages:
  - run
  
run-sanity-tests:
  image:
    name: python:3.9.6
  stage: run
  script:
    - apt -y update
    - apt -y upgrade
    - apt-get -y install xvfb
    - export DISPLAY=:0
    - Xvfb :0 -ac -screen 0 2560x1440x24 -nolisten tcp &
    - wget https://dl.google.com/linux/direct/google-chrome-stable_current_amd64.deb
    - apt install -y ./google-chrome-stable_current_amd64.deb
    - pip3 install -r requirements.txt
    - seleniumbase install chromedriver latest
    - pytest -m 'sanity' --gui --maximize-window --testEnv="$ENVIRONMENT" --reuse-session --gherkin-terminal-reporter --no-header --color=yes --code-highlight=yes -vv
  tags:
    - large
  only:
    - triggers

Thanks in advance for any answers!

[mdmintz]

Hello @shivabhardwaj18,

The Chromium Team changed how they packaged Chromedriver in version 109 (They added a new License file into the zip file, where previously there was only the chromedriver executable). There was a ticket already filed for this: #1663, and it was fixed in 4.11.3 - https://github.com/seleniumbase/SeleniumBase/releases/tag/v4.11.3.

The latest version of SeleniumBase is 4.12.2 right now, so you should probably just upgrade directly to that, and your issue will be fixed.

[shivabhardwaj18]

Thanks a lot Michael! Updating seleniumbase to 4.12.2 and pytest to 7.2.1 did resolve my issue.