Malin
ea70d34d7f
Our start.sh was starting Xvfb on :99, then sitespeed.io tried to start its own on :99, failed with exit code 1, and Chrome couldn't get a working display. sitespeed.io is designed to manage Xvfb per test run. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
15 lines
373 B
Bash
15 lines
373 B
Bash
#!/bin/bash
|
|
set -e
|
|
|
|
# Load the sitespeed.io binary path discovered at build time
|
|
if [ -f /sitespeed_env ]; then
|
|
source /sitespeed_env
|
|
fi
|
|
|
|
echo "[start.sh] SITESPEED_BIN=${SITESPEED_BIN:-NOT FOUND}"
|
|
|
|
# Do NOT start Xvfb here — sitespeed.io starts its own Xvfb instance
|
|
# per test run. Starting one here causes a conflict on :99 and breaks Chrome.
|
|
|
|
exec node /app/app.js
|