Error when running Travis CI with Wallaby

I’m experiencing an issue right now with test failures only on Travis CI. Because things are only failing on Travis it leads me to believe something is wrong with Chromium or my .travis.yml file. Here is the error:

 ** (exit) exited in: GenServer.call(Wallaby.Driver.LogStore, {:get_and_update, #Function<0.5365077/1 in Wallaby.Driver.LogStore.append_logs/2>}, 5000)
         ** (EXIT) an exception was raised:
             ** (ArgumentError) argument error
                 :erlang.--(%{"error" => "invalid session id", "message" => "invalid session id", "stacktrace" => "#0 0x5594ce309749 <unknown>\n"}, [])
                 (wallaby) lib/wallaby/driver/log_store.ex:25: Wallaby.Driver.LogStore.unique_logs/2
                 (elixir) lib/map.ex:791: Map.get_and_update/3
                 (elixir) lib/agent/server.ex:16: Agent.Server.handle_call/3
                 (stdlib) gen_server.erl:661: :gen_server.try_handle_call/4
                 (stdlib) gen_server.erl:690: :gen_server.handle_msg/6
                 (stdlib) proc_lib.erl:249: :proc_lib.init_p_do_apply/3

And here is my travis.yml file:

 language: elixir
dist: xenial

env:
  MIX_ENV: test
  S3_BUCKET: dream-house-staging

elixir: 1.7.3
otp_release: 21.1

addons:
  chrome: stable
  postgresql: "10"

before_install:
  - google-chrome-stable --headless --disable-gpu --remote-debugging-port=9222 http://localhost &

before_script:
  - mix do ecto.create, ecto.migrate
  - gem install fakes3 -v "1.2.1"
  - fakes3 -r $HOME/.s3bucket -p 4567 &
  - curl -s https://chromedriver.storage.googleapis.com/76.0.3809.68/chromedriver_linux64.zip | zcat > $HOME/bin/chromedriver
  - chmod +x $HOME/bin/chromedriver

after_script:
  — kill $(pgrep -f fakes3)

branches:
  only:
    - master

notifications:
  webhooks:
    on_start: always

I really can’t figure out what is wrong here. Any help would be great! Thank you!

1 Like

This happens when you have a mismatch between your chromedriver version and the chromium version. How are you installing chromedriver? If via yarn, can you show your yarn.lock file?

3 Likes

Hey Ben, I was actually able to solve this by simply updating the Chrome Driver version. So, you were totally correct.

1 Like