Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

Excessive CPU Utilization when using Percy Playwright #1066

Closed
unlikelyzero opened this issue Sep 13, 2022 · 0 comments
Closed

Excessive CPU Utilization when using Percy Playwright #1066

unlikelyzero opened this issue Sep 13, 2022 · 0 comments

Comments

@unlikelyzero
Copy link

unlikelyzero commented Sep 13, 2022

The problem

We are peeling the onion on some percy cli flakiness found on #1065 and noticed that the CPU utilization of the running process is exceeding the resources available on the basic Circle CI Agent.

CPU Utilization with percy exec enabled

Screen Shot 2022-09-13 at 9 49 17 AM

This is the exact same test run but with percy exec disabled

Screen Shot 2022-09-13 at 10 37 12 AM

Environment

  • Node version: 16
  • @percy/cli version: 1.7.2
  • OS version: ubuntu focal image

Details

We are using a pretty standard percy integration with playwright. It appears that the CPU is pegged at 100% for the majority of the tests being executed despite lowering the CPU impact by:

  1. Disabling all diagnostic tooling from playwright (tracefile, screenshot, video, debug mode)
  2. Running a single worker and single test at a time.

Debug logs

https://app.circleci.com/pipelines/github/nasa/openmct/13351/workflows/2c27db3f-cdba-44d6-8651-0aadb149f377/jobs/50220/resources

Code to reproduce issue

#1065

@percy percy locked and limited conversation to collaborators Sep 13, 2022
@Robdel12 Robdel12 converted this issue into discussion #1067 Sep 13, 2022

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant