QABattle

Selenium / Scenario

Grid Down: The Monday Morning Queue

Forty parallel sessions requested, twelve slots alive, a node that lies about its health, and a queue quietly eating session requests. Restore the Grid before standup.

Difficulty
Hard
Format
Scenario
Points
200
Estimate
16 min

// MISSION BRIEF

Your Mission

Monday, 08:40. The overnight regression died at 03:12 with a wall of session-creation timeouts, and the morning smoke run is now hanging too. You have the Grid status output, node logs, and the suite config.

Work the outage: read the topology, find the lying node, and fix the capacity math. Decisions are weighted.

// FIRST CONTACT

Battle teaser

First artifact

grid /status (summarized)

Node-3 reports healthy with 0 sessions but its log shows 57 Chrome startup crashes. What is happening?

  1. AThe router is corrupting requests to Node-3 only
  2. BNode heartbeat measures the node PROCESS, not browser startability; Node-3's Chrome/chromedriver version mismatch makes every session attempt fail, so the distributor keeps offering slots that always crash, a black-hole node
  3. CNode-3 is fine; 0 sessions means it is just idle
Answers, scoring, hints, and the full battle stay sealed.

// SKILL TAGS

seleniumgridinfrastructureincident-responseparallel-execution