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.

Sign up for GitHub

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

Jump to bottom

investigate why windows create_amplify e2e test takes so long #1198

Open
edwardfoyle opened this issue Mar 22, 2024 · 0 comments
Open

investigate why windows create_amplify e2e test takes so long #1198

edwardfoyle opened this issue Mar 22, 2024 · 0 comments
Labels
repo-infrastructure Engineering label for issues related to repo infrastructure tech-debt Refactors, unsavory workarounds or other technical decisions that should be revisited later testing Engineering label for issues related to tests or test tooling

Comments

@edwardfoyle
Copy link
Contributor

edwardfoyle commented Mar 22, 2024 •
edited
Loading

Description

The windows e2e_create_amplify job takes significantly longer than the same job runnin on mac and linux. For some reason the npm install from the local verdaccio server is very slow (> 10 minutes to install the packages). We should figure out why this is so slow and/or figure out some other strategy to speed things along.
@edwardfoyle edwardfoyle added testing Engineering label for issues related to tests or test tooling repo-infrastructure Engineering label for issues related to repo infrastructure labels Mar 22, 2024
@edwardfoyle edwardfoyle mentioned this issue Mar 22, 2024
Merged
@josefaidt josefaidt added the tech-debt Refactors, unsavory workarounds or other technical decisions that should be revisited later label Apr 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
repo-infrastructure Engineering label for issues related to repo infrastructure tech-debt Refactors, unsavory workarounds or other technical decisions that should be revisited later testing Engineering label for issues related to tests or test tooling
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@josefaidt @edwardfoyle