[Feature] Support Ubuntu 22.04 #13738
Assignees
Comments
|
fyi- ubuntu 22.x install-deps fails. it seems as some packages were renamed: ttf-unifont -> fonts-unifont that's as far as i get before the script aborts. |
This was referenced May 4, 2022
|
For the failures on jammy (22.04LTS): I did some digging: libenchant1c2a > libenchant-2-2 |
Closed
This was referenced Jun 2, 2022
This was referenced Jun 7, 2022
This was referenced Jun 9, 2022
|
Thats done! For further issues, please file new issues on GitHub. It gets released in 1.23. |
|
When will version 1.23 be released? Or is there a way to run playwright on Ubuntu 22.04 ahead of time? I can't wait to try out such a great framework. 🙂 |
or
We'll release in 1-2 weeks I guess. |
2 tasks
11 tasks
kodiakhq bot
pushed a commit
to vercel/next.js
that referenced
this issue
Dec 7, 2022
## Bug Test(Production) CI fails with error ``` Package libicu66 is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source E: Package 'ttf-unifont' has no installation candidate E: Package 'ttf-ubuntu-font-family' has no installation candidate E: Unable to locate package libenchant1c2a E: Package 'libicu66' has no installation candidate E: Unable to locate package libvpx6 E: Unable to locate package libwebp6 Failed to install browser dependencies ``` This is due to new release for the runner image (actions/runner-images#6399) now sets ubuntu 22.04 as latest, but playwright have release to support it (microsoft/playwright#13738) but @replayio/playwright seems not picked it up yet (https://github.com/replayio/replay-cli/blob/main/packages/playwright/package.json#L23) PR tries to pin to known working image (20.04) until dependencies can support new image gracefully. - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Errors have a helpful link attached, see [`contributing.md`](https://github.com/vercel/next.js/blob/canary/contributing.md) ## Feature - [ ] Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. - [ ] Related issues linked using `fixes #number` - [ ] [e2e](https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) tests added - [ ] Documentation added - [ ] Telemetry added. In case of a feature if it's used or not. - [ ] Errors have a helpful link attached, see [`contributing.md`](https://github.com/vercel/next.js/blob/canary/contributing.md) ## Documentation / Examples - [ ] Make sure the linting passes by running `pnpm build && pnpm lint` - [ ] The "examples guidelines" are followed from [our contributing doc](https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md)
|
If you are like me googling for your error, here is what helped me (I am on 22.04.1 lts based kde neon which playwright reports as unsupported OS): |
|
I'm still receiving the following errors when running |
Try to upgrade Playwright. |
|
Im running playwright in a Github action that does not have a pre-existing install of PlayWright (see workflow example below). Doesnt end_to_end_test:
name: End to End Test
# Runs on an ubuntu runner
needs: [build_and_deploy_job]
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v3
- uses: actions/setup-node@v3
- name: Install dependencies
run: npm ci
- name: Install Playwright
run: npx [email protected] install --with-deps
- name: Build production build
run: npm run build
- name: Run your tests
run: npm run playwright_test |
|
apologies, it looks like the issue was I had playwright defined in my package.json as well so when running playwright it was using the old version in there that does not support the the latest ubuntu |
|
Hello, Now with Ubuntu 24.04 around the corner, may I ask please if there is already a plan or roadmap for when we can have it in a Playwright workflow? |
|
I was still hitting a similar issue above, where the installation fails shortly after what appears to be the output of a |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Blocked by:
Requires the following changes so far:
don't suggest focal in the docs anymore, suggest 22.The text was updated successfully, but these errors were encountered: