Page MenuHomePhabricator

Investigate why increasing maxInstances for WebdriverIO causes tests to fail
Closed, InvalidPublic5 Estimated Story PointsSpike

Description

In T402397: Increase maxInstances for WebdriverIO test in core I have noticed that increasing maxInstances for WebdriverIO causes tests to fail.

AC

  • find out if the same tests fail all the time, or if there is no pattern
  • if there is a pattern, find out what is causing the failures
  • if the problem is found, create a follow up task where we try to fix the problem
  • test in core
  • test in at least one extension (examples)
  • check if updating webdriverio to the latest v9 helps
  • The questions above are answered in the comments to this ticket
  • If issues are identified, follow up tickets are created in the backlog

Event Timeline

My ideas:

  • try with one instance but throttle cpu artificially by some method to see if flakiness is consistent
  • play chrome flags like the following:
Memory and Resource Management

--disable-dev-shm-usage
--memory-pressure-off
--max_old_space_size=4096
--disable-background-timer-throttling
--disable-renderer-backgrounding
--disable-features=TranslateUI
--disable-ipc-flooding-protection

GPU and Rendering

--disable-gpu
--disable-gpu-sandbox
--no-sandbox
--disable-setuid-sandbox
--disable-accelerated-2d-canvas
--disable-web-security
--disable-features=VizDisplayCompositor

Process Isolation

--disable-site-isolation-trials
--disable-features=IsolateOrigins,site-per-process
--process-per-site
--single-process

Performance and Stability

--disable-blink-features=AutomationControlled
--disable-extensions
--disable-plugins
--disable-images
--disable-javascript
--mute-audio
--no-first-run
--no-default-browser-check
--disable-background-networking
--disable-sync
--disable-translate
--metrics-recording-only
--safebrowsing-disable-auto-update
--disable-component-update

Crash Prevention

--disable-hang-monitor
--disable-prompt-on-repost
--disable-domain-reliability
--disable-features=AudioServiceOutOfProcess
--disable-print-preview
--disable-crash-reporter
--disable-breakpad
--disable-logging

Let me know if you need help to throttle the CPU. We do that today on the performance synthetic machines. Those machines are Intel based and runs Ubuntu. I think it would be a nice feature to run all our tests on a "slow" device to be able to see tests that is dependent of a fast CPU.

zeljkofilipin renamed this task from Investigate why increasing maxInstances for WebdriverIO test in core causes tests to fail to Investigate why increasing maxInstances for WebdriverIO tests causes tests to fail.Nov 20 2025, 2:30 PM
zeljkofilipin renamed this task from Investigate why increasing maxInstances for WebdriverIO tests causes tests to fail to Investigate why increasing maxInstances for WebdriverIO causes tests to fail.Nov 20 2025, 2:32 PM
zeljkofilipin updated the task description. (Show Details)
Restricted Application changed the subtype of this task from "Task" to "Spike". · View Herald TranscriptNov 24 2025, 4:48 PM

Generally my recollection is keeping the number of browser instances less than or equal to the number of cpu cores is best

RAM pressure is also good to keep an eye on - not exceeding available ram, as usual, is desirable