-
Notifications
You must be signed in to change notification settings - Fork 3.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Running Nightly as root in a regular user's session is not supported. #6500
Comments
@aslushnikov for help with docker. The code in firefox is in |
Thanks @JoelEinbinder that solved the issue 👍 |
Update: I raised an issue on GitHub side, since it seems not fixable on our side except using |
Looks like the workaround is good-enough |
This workaround is based on issue microsoft/playwright#6500
Reopening since this is still relevant and affects the default configuration. Repro: https://github.com/mxschmitt/firefox-github-actions-container Actually while looking at it again, it seems working fine: https://github.com/mxschmitt/firefox-github-actions-container Waiting for new customer reports. |
I saw this occur when using the container as a GitHub Actions step: #23388 (comment). GitHub Actions passes in a I tried to override it at the step level (PREreview/prereview.org@8f7b96e), but it didn't apply (it remained Following #23388 (comment), using I couldn't recreate this locally with Act, and I haven't seen it when using |
@thewilkybarkid could you help me reproducing it at the https://github.com/mxschmitt/firefox-github-actions-container repository? (feel free to create a PR there with what I did wrong) |
@thewilkybarkid could you please try running |
@aslushnikov Yeah, that does get round the problem:
|
@thewilkybarkid that's the way to go then. Supplying I'll close this with the given workaround since it seems to be good-enough! |
If possible, it'd be great if someone had a moment to update the docs at the following two locations: |
@taylorkline feel free to send us a pull request! |
* Add playwright workflow * Add html reporter to test workflow * use playwright image for Github action * Use selected fonts for consistency and reproducability * Update playwright * Workaround for root issue microsoft/playwright#6500
- attempting solution from https://github.com/mxschmitt/firefox-github-actions-container/pull/3/files - thread: microsoft/playwright#6500
* Setup Playwright with common browsers * Update gitignore to add trace files * chore: update deps [next 13.5] * e2e testing on push/pull playwright - Testing via containers to run Playwright Tests * adding pnpm to install dependencies - Changed install dependencies step to use pnpm actions * fix missing dependencies and change to pnpm - Attempt to fix missing msedge - Change all npm commands to execute via pnpm * fix: nightly cannot be run from root - attempting solution from https://github.com/mxschmitt/firefox-github-actions-container/pull/3/files - thread: microsoft/playwright#6500 * feat: On Deploy Playwright Testing & Modify Push/pull for Main Only - On Deploy (Preview and Production), Run Playwright E2E Tests - Modify Push/Pull to run Playwright E2E Tests only on main/master * fix: Improve Job Names in Worflow Runs - Changed Job Names under each playwright testing environment * fix: Deployment URL is not being hit when Playwright E2E Tests are run - added Deployment URL via env variable in URL attribute of playwright config * improve: Removed Redundant Testing Stage & Switched TO E2E Tests on Preview Deployments - Due to the nature of Vercel Preview, it creates preview deployments for all branches associated to the project. As such, the E2E tests run on all branches for which Vercel releases a deployment for (including preview) which applies to every branch. - We will get stability coverage across all branches on all pushes across the project. As such, it is not necessary to build and execute a web server on a container to E2E test again. As the build and execute process is automatically tested and reported by Vercel. * Removed WebServer from Playwright - Running into an issue where WebServer causes issues on workflow run after deployment with "reuseExistingServer" & URL / Port Already active - Decided to change local E2E Testing policy to run `pnpm run dev` on a separate terminal & run pnpm exec playwright test on a separate terminal * attempt: determining if pnpm commands can execute playwright tests on deploy * attempt: Playwright Package Missing Fix * attempt: fix yaml syntax * fix: Update test to use baseURL * improve: Added Type Documentation for PLAYWRIGHT_TEST_BASE_URL
microsoft#6500 Signed-off-by: Jozef Hollý <[email protected]>
Reference: #6500 (#6500 (comment)) It seems that this is now required, so this PR applies that to the docs. Signed-off-by: Jozef Hollý <[email protected]>
* use pre-installed playwritght container for widget-tests * use HOME=root workaround for firefox -> see microsoft/playwright#6500 (thanks, @thewilkybarkid !)
* Refactor project structure * Update to nuxt v3 * Fix build * Fix categorization and links * Remove file that should be ignored * Fix build * Fix test run * Update CI tasks - Increment versions to improve performance and upload the right directory * Fix dependency tree * Allow optional dependencies to be installed * Regenerate package lock * Fix artifact download version * Fix feature test step * Add workaround for browser... - See: microsoft/playwright#6500 * Ensure we don't build twice for tests
Running playwright automation in Github CI using docker image fails for Firefox
Github Actions Workflow looks as follow:
Output is:
The text was updated successfully, but these errors were encountered: