chore(test): adds --no-sandbox to testing to prevent gh hang

This follows the suggestion as seen in the error message on the ghaction: Run npm test > [email protected] test > node test/server.js Failed to launch the browser process! [2359:2359:0107/175821.608019:FATAL:zygote_host_impl_linux.cc(126)] No usable sandbox! Update your kernel or see https://chromium.googlesource.com/chromium/src/+/main/docs/linux/suid_sandbox_development.md for more information on developing with the SUID sandbox. If you want to live dangerously and need an immediate workaround, you can try using --no-sandbox.
NCEAS · Jan 7, 2025 · 36f6e2c · 36f6e2c
1 parent 1c98d96
commit 36f6e2c
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/test/server.js b/test/server.js
@@ -43,7 +43,7 @@ const server = app.listen(port);
 url = "http://localhost:" + port + url;
 
 async function runTests(url) {
-  const browser = await puppeteer.launch({ headless: true });
+  const browser = await puppeteer.launch({ headless: true, args: ['--no-sandbox', '--disable-setuid-sandbox'] });
   const page = await browser.newPage();
   await page.goto(url, { waitUntil: "networkidle0" });
   const html = await page.content(); // serialized HTML of page DOM.