Skip to content
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

Update wait-on-vite example to current versions #758

Merged
merged 1 commit into from
Feb 13, 2023

Conversation

MikeMcC399
Copy link
Collaborator

@MikeMcC399 MikeMcC399 commented Jan 30, 2023

This PR implements the suggestion from issue #756 "examples/wait-on-vite uses vite 2 beta" to update the Vite version to a non-beta version.

For the legacy (v9) and current config example versions, the wait-on-vite app is replaced by the standard example created by npm create vite with options Vanilla and JavaScript.

In .github/workflows/example-wait-on.yml changes are made to align with default Vite values / settings:

Item Old New
port 3000 5173
start server npm start npm run dev

Verification

Local test

Execute:

cd examples/wait-on-vite
npm ci
npm run dev

Check that server announces itself with VITE v4.0.4.

In a separate terminal window execute:

cd examples/wait-on-vite
npm test

ensuring that the Cypress test runs successfully.

In the server terminal window, press q to quit the server.

cd ../v9/wait-on-vite
npm ci
npm run dev

Check that server announces itself with VITE v3.2.5.

Switch to the separate test terminal window and execute:

cd ../v9/wait-on-vite
npm test

and ensure that the Cypress test for the v9 version runs successfully.

GitHub Action test

Run .github/workflows/example-wait-on.yml and check that jobs

  • wait-on-vite-v9 and
  • wait-on-vite

show success.

@MikeMcC399

This comment was marked as outdated.

@MikeMcC399 MikeMcC399 force-pushed the update/wait-on-vite branch 2 times, most recently from 1d5d312 to 0a0a13a Compare February 8, 2023 05:40
@MikeMcC399 MikeMcC399 marked this pull request as ready for review February 8, 2023 05:51
updates wait-on-vite to use Vite 4
updates v9/wait-on-vite to use Vite 3
app code is standard from npm create vite
port is changed to default 5173
@jaffrepaul
Copy link
Contributor

This looks goo @MikeMcC399. Have you uncovered any intel on the errors indicated here? https://github.com/cypress-io/github-action/actions/runs/4143979840/jobs/7166507634#step:3:47

@MikeMcC399
Copy link
Collaborator Author

@jaffrepaul

Have you uncovered any intel on the errors indicated here?

This is a general Cypress issue related to running under GitHub runners or Docker containers.

Cypress 12.x

Under Cypress 12.4.1 with ubuntu-20.04

[1867:0210/202930.349866:ERROR:gpu_memory_buffer_support_x11.cc(44)] dri3 extension not supported.

and ubuntu-22.04 GitHub runners an error message always appears:

[1861:0210/202926.180966:ERROR:gpu_memory_buffer_support_x11.cc(44)] dri3 extension not supported.

Cypress 9.7.0

Under Cypress 9.7.0 with ubuntu-20.04 and ubuntu-22.04 an additional message "ERROR:sandbox_linux.cc(377)" is output:

[2228:0210/124337.097768:ERROR:sandbox_linux.cc(377)] InitializeSandbox() called with multiple threads in process gpu-process.
[2228:0210/124337.106162:ERROR:gpu_memory_buffer_support_x11.cc(44)] dri3 extension not supported.

Neither errors prevent Cypress tests from succeeding.

@lmiller1990
Copy link
Contributor

We generally won't backport any fixes to olde versions of Cypress - since that one you are referring to is purely cosmetic, non a blocker to running tests, I think it's fine to move forward as is.

@jaffrepaul
Copy link
Contributor

Thanks for clarifying @MikeMcC399!

@jaffrepaul jaffrepaul merged commit 290755b into cypress-io:master Feb 13, 2023
@MikeMcC399 MikeMcC399 deleted the update/wait-on-vite branch February 13, 2023 15:59
@MikeMcC399
Copy link
Collaborator Author

@jaffrepaul

It seems that there is a recording clash happening when multiple actions, like ones triggered by a PR here, and others triggered by the renovate process are running in parallel. This causes test failures in

Could you perhaps change the renovate schedule so it doesn't try to create new PRs at the same time as you would potentially be merging PRs?

@jaffrepaul
Copy link
Contributor

Yes. I've seen this happen before, but haven't had the bandwidth to get to the root cause. Will get a look at renovate config as a possible solution.

@github-actions
Copy link

🎉 This PR is included in version 5.0.9 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants