Alex Rudenko
Alex Rudenko
Ah, I see. Which version is `/usr/bin/chromium`?
@Lightning00Blade FYI I have updated this to use setup.exe but it should start working only with M127
I believe it might but we are not testing with Chromium anymore. Does the same workaround help?
@kblok the workaround without setup.exe is documented here https://pptr.dev/troubleshooting#chrome-reports-sandbox-errors-on-windows
we might also file a request to include setup.exe into Chromium, let me look into that
let's see if the reviewers have any comments https://chromium-review.googlesource.com/c/chromium/src/+/5764985
``` import puppeteer from 'puppeteer'; const browser = await puppeteer.launch(); const page = await browser.newPage(); page.on('requestfailed', requestfailed => { var req=JSON.stringify(requestfailed.failure()) console.log('requestfailed occurred: ', req); }) await page.goto('https://books.toscrape.com/catalogue/category/books/add-a-comment_18/index.html') ``` still...
The tools unit tests failure already exists on the main branch (PR to reproduce the issue https://github.com/web-platform-tests/wpt/pull/46348).
I have updated the PR but publishing a new image tagged `1` failed because launchpad.net is under maintenance so `apt-add-repository -y ppa:deadsnakes/ppa` fails. Related: https://askubuntu.com/a/1398569/374747
I think this PR is ready for review. Apart from landing this PR, an admin should set permissions on the package as documented in the linked RFC https://github.com/web-platform-tests/rfcs/pull/198