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

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

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:
- Disabling all diagnostic tooling from playwright (tracefile, screenshot, video, debug mode)
- 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
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 execenabledThis is the exact same test run but with
percy execdisabledEnvironment
@percy/cliversion: 1.7.2Details
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:
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