Skip to content

YC (S26) | Open Computer History | Continuously record your company computer work, map your workflows, help you find work worth automating, and power your agents' context

test(e2e): skip headless owned-browser drive under CI (off-screen webview can't run JS)

Louis Beaumontb4978008f743
diff --git a/apps/screenpipe-app-tauri/e2e/specs/zzz-owned-browser-headless.spec.ts b/apps/screenpipe-app-tauri/e2e/specs/zzz-owned-browser-headless.spec.ts
index 975cad771..8ddbca01e 100644
--- a/apps/screenpipe-app-tauri/e2e/specs/zzz-owned-browser-headless.spec.ts
+++ b/apps/screenpipe-app-tauri/e2e/specs/zzz-owned-browser-headless.spec.ts
@@ -50,7 +50,17 @@ import {
} from "../helpers/tauri.js";
import { authHeaders, getLocalApiConfig } from "../helpers/api-utils.js";
-const canDriveOwnedBrowser = process.platform !== "linux";
+// The headless drive hosts an OFF-SCREEN background webview (owned-browser-bg-host)
+// and evals JS inside it. That needs a real window server / compositor: on GitHub's
+// hosted macOS + Windows runners (headless, virtual display) a fully off-screen
+// webview never executes JS, so `ensure_background_child` never becomes serviceable
+// and the eval returns 502 "child webview not attached". It fails 100% of CI runs
+// there yet works on a real display (where #4262 was validated), so keep the spec
+// runnable LOCALLY and skip it under CI. Linux (WebKitGTK) can't drive the owned
+// browser headlessly at all, hence the original platform guard. Making the headless
+// host CI-driveable (e.g. an on-screen-but-tiny host under the e2e feature) is a
+// follow-up on the #4262 owner.
+const canDriveOwnedBrowser = process.platform !== "linux" && !process.env.CI;
const OWNED_ID = "owned-default";
const READY_STATES = ["loading", "interactive", "complete"];