Specifics for Mac OS with M1, M2 processors & Docker Desktop

You might encounter the following errors when running tests locally, using Gitlab QA, on Mac OS with M1 or M2 processors. These errors usually stem from using Docker images that are based on Linux/AMD64 platforms.

• MADV_DONTNEED does not work (memset will be used instead)

  : MADV_DONTNEED does not work (memset will be used instead)
  : (This is the expected behaviour if you are running under QEMU)
  bundler: failed to load command: bin/qa (bin/qa)
  #0 0x004000724133 : unknown error: Chrome failed to start: crashed. (Selenium::WebDriver::Error::UnknownError)
      (unknown error: DevToolsActivePort file doesn't exist)
      (The process started from chrome location /usr/bin/google-chrome is no longer running,
      so ChromeDriver is assuming that Chrome has crashed.)
  

• QA::Support::Repeater::WaitExceededError

  QA::Support::Repeater::WaitExceededError:
      Page did not fully load. This could be due to an unending async request or loading icon.
  

• Selenium::WebDriver::Error::UnknownError

  Selenium::WebDriver::Error::UnknownError:
      unknown error: session deleted because of page crash
      from tab crashed
      (Session info: headless chrome=113.0.5672.126)
  

To resolve these issues:

1. Do not use /dev/shm shared memory. Set CHROME_DISABLE_DEV_SHM environment variable to true. shell $ export CHROME_DISABLE_DEV_SHM=true # Disable Chrome shared memory
2. Enable Use Rosetta for x86/amd64 emulation on Apple Silicon option in Docker (Using Docker Desktop ~v4.22.1).
   1. Open Settings in Docker Desktop
   2. Go to Features in development
   3. Enable Use Rosetta for x86/amd64 emulation on Apple Silicon setting
   4. Select Apply & restart