chore: optimize ai e2e test (#99) #133
Annotations
10 errors and 1 warning
tests/unit-test/web-extractor.test.ts > extractor > basic:
packages/web-integration/tests/ai/web/puppeteer/utils.ts#L12
Error: Could not find Chrome (ver. 127.0.6533.99). This can occur if either
1. you did not perform an installation before running the script (e.g. `npx puppeteer browsers install chrome`) or
2. your cache path is incorrectly configured (which is: /home/runner/.cache/puppeteer).
For (2), check out our guide on configuring puppeteer at https://pptr.dev/guides/configuration.
❯ ChromeLauncher.resolveExecutablePath ../../node_modules/.pnpm/[email protected]/node_modules/puppeteer-core/src/node/BrowserLauncher.ts:443:17
❯ ChromeLauncher.executablePath ../../node_modules/.pnpm/[email protected]/node_modules/puppeteer-core/src/node/ChromeLauncher.ts:280:19
❯ ChromeLauncher.computeLaunchArguments ../../node_modules/.pnpm/[email protected]/node_modules/puppeteer-core/src/node/ChromeLauncher.ts:130:31
❯ ChromeLauncher.launch ../../node_modules/.pnpm/[email protected]/node_modules/puppeteer-core/src/node/BrowserLauncher.ts:100:24
❯ Module.launchPage tests/ai/web/puppeteer/utils.ts:12:19
❯ tests/unit-test/web-extractor.test.ts:14:31
|
tests/unit-test/web-extractor.test.ts > extractor > check screenshot size - 1x:
packages/web-integration/tests/ai/web/puppeteer/utils.ts#L12
Error: Could not find Chrome (ver. 127.0.6533.99). This can occur if either
1. you did not perform an installation before running the script (e.g. `npx puppeteer browsers install chrome`) or
2. your cache path is incorrectly configured (which is: /home/runner/.cache/puppeteer).
For (2), check out our guide on configuring puppeteer at https://pptr.dev/guides/configuration.
❯ ChromeLauncher.resolveExecutablePath ../../node_modules/.pnpm/[email protected]/node_modules/puppeteer-core/src/node/BrowserLauncher.ts:443:17
❯ ChromeLauncher.executablePath ../../node_modules/.pnpm/[email protected]/node_modules/puppeteer-core/src/node/ChromeLauncher.ts:280:19
❯ ChromeLauncher.computeLaunchArguments ../../node_modules/.pnpm/[email protected]/node_modules/puppeteer-core/src/node/ChromeLauncher.ts:130:31
❯ ChromeLauncher.launch ../../node_modules/.pnpm/[email protected]/node_modules/puppeteer-core/src/node/BrowserLauncher.ts:100:24
❯ Module.launchPage tests/ai/web/puppeteer/utils.ts:12:19
❯ tests/unit-test/web-extractor.test.ts:46:31
|
tests/unit-test/web-extractor.test.ts > extractor > check screenshot size - 2x:
packages/web-integration/tests/ai/web/puppeteer/utils.ts#L12
Error: Could not find Chrome (ver. 127.0.6533.99). This can occur if either
1. you did not perform an installation before running the script (e.g. `npx puppeteer browsers install chrome`) or
2. your cache path is incorrectly configured (which is: /home/runner/.cache/puppeteer).
For (2), check out our guide on configuring puppeteer at https://pptr.dev/guides/configuration.
❯ ChromeLauncher.resolveExecutablePath ../../node_modules/.pnpm/[email protected]/node_modules/puppeteer-core/src/node/BrowserLauncher.ts:443:17
❯ ChromeLauncher.executablePath ../../node_modules/.pnpm/[email protected]/node_modules/puppeteer-core/src/node/ChromeLauncher.ts:280:19
❯ ChromeLauncher.computeLaunchArguments ../../node_modules/.pnpm/[email protected]/node_modules/puppeteer-core/src/node/ChromeLauncher.ts:130:31
❯ ChromeLauncher.launch ../../node_modules/.pnpm/[email protected]/node_modules/puppeteer-core/src/node/BrowserLauncher.ts:100:24
❯ Module.launchPage tests/ai/web/puppeteer/utils.ts:12:19
❯ tests/unit-test/web-extractor.test.ts:63:31
|
tests/unit-test/web-extractor.test.ts > extractor > scroll:
packages/web-integration/tests/ai/web/puppeteer/utils.ts#L12
Error: Could not find Chrome (ver. 127.0.6533.99). This can occur if either
1. you did not perform an installation before running the script (e.g. `npx puppeteer browsers install chrome`) or
2. your cache path is incorrectly configured (which is: /home/runner/.cache/puppeteer).
For (2), check out our guide on configuring puppeteer at https://pptr.dev/guides/configuration.
❯ ChromeLauncher.resolveExecutablePath ../../node_modules/.pnpm/[email protected]/node_modules/puppeteer-core/src/node/BrowserLauncher.ts:443:17
❯ ChromeLauncher.executablePath ../../node_modules/.pnpm/[email protected]/node_modules/puppeteer-core/src/node/ChromeLauncher.ts:280:19
❯ ChromeLauncher.computeLaunchArguments ../../node_modules/.pnpm/[email protected]/node_modules/puppeteer-core/src/node/ChromeLauncher.ts:130:31
❯ ChromeLauncher.launch ../../node_modules/.pnpm/[email protected]/node_modules/puppeteer-core/src/node/BrowserLauncher.ts:100:24
❯ Module.launchPage tests/ai/web/puppeteer/utils.ts:12:19
❯ tests/unit-test/web-extractor.test.ts:80:31
|
tests/unit-test/web-extractor.test.ts > extractor > profile :
packages/web-integration/tests/ai/web/puppeteer/utils.ts#L12
Error: Could not find Chrome (ver. 127.0.6533.99). This can occur if either
1. you did not perform an installation before running the script (e.g. `npx puppeteer browsers install chrome`) or
2. your cache path is incorrectly configured (which is: /home/runner/.cache/puppeteer).
For (2), check out our guide on configuring puppeteer at https://pptr.dev/guides/configuration.
❯ ChromeLauncher.resolveExecutablePath ../../node_modules/.pnpm/[email protected]/node_modules/puppeteer-core/src/node/BrowserLauncher.ts:443:17
❯ ChromeLauncher.executablePath ../../node_modules/.pnpm/[email protected]/node_modules/puppeteer-core/src/node/ChromeLauncher.ts:280:19
❯ ChromeLauncher.computeLaunchArguments ../../node_modules/.pnpm/[email protected]/node_modules/puppeteer-core/src/node/ChromeLauncher.ts:130:31
❯ ChromeLauncher.launch ../../node_modules/.pnpm/[email protected]/node_modules/puppeteer-core/src/node/BrowserLauncher.ts:100:24
❯ Module.launchPage tests/ai/web/puppeteer/utils.ts:12:19
❯ tests/unit-test/web-extractor.test.ts:103:31
|
tests/ai/web/puppeteer/showcase.test.ts > puppeteer integration > Sauce Demo by Swag Lab:
packages/web-integration/tests/ai/web/puppeteer/utils.ts#L12
Error: Could not find Chrome (ver. 127.0.6533.99). This can occur if either
1. you did not perform an installation before running the script (e.g. `npx puppeteer browsers install chrome`) or
2. your cache path is incorrectly configured (which is: /home/runner/.cache/puppeteer).
For (2), check out our guide on configuring puppeteer at https://pptr.dev/guides/configuration.
❯ ChromeLauncher.resolveExecutablePath ../../node_modules/.pnpm/[email protected]/node_modules/puppeteer-core/src/node/BrowserLauncher.ts:443:17
❯ ChromeLauncher.executablePath ../../node_modules/.pnpm/[email protected]/node_modules/puppeteer-core/src/node/ChromeLauncher.ts:280:19
❯ ChromeLauncher.computeLaunchArguments ../../node_modules/.pnpm/[email protected]/node_modules/puppeteer-core/src/node/ChromeLauncher.ts:130:31
❯ ChromeLauncher.launch ../../node_modules/.pnpm/[email protected]/node_modules/puppeteer-core/src/node/BrowserLauncher.ts:100:24
❯ Module.launchPage tests/ai/web/puppeteer/utils.ts:12:19
❯ tests/ai/web/puppeteer/showcase.test.ts:9:37
|
tests/ai/web/puppeteer/showcase.test.ts > puppeteer integration > extract the Github service status:
packages/web-integration/tests/ai/web/puppeteer/utils.ts#L12
Error: Could not find Chrome (ver. 127.0.6533.99). This can occur if either
1. you did not perform an installation before running the script (e.g. `npx puppeteer browsers install chrome`) or
2. your cache path is incorrectly configured (which is: /home/runner/.cache/puppeteer).
For (2), check out our guide on configuring puppeteer at https://pptr.dev/guides/configuration.
❯ ChromeLauncher.resolveExecutablePath ../../node_modules/.pnpm/[email protected]/node_modules/puppeteer-core/src/node/BrowserLauncher.ts:443:17
❯ ChromeLauncher.executablePath ../../node_modules/.pnpm/[email protected]/node_modules/puppeteer-core/src/node/ChromeLauncher.ts:280:19
❯ ChromeLauncher.computeLaunchArguments ../../node_modules/.pnpm/[email protected]/node_modules/puppeteer-core/src/node/ChromeLauncher.ts:130:31
❯ ChromeLauncher.launch ../../node_modules/.pnpm/[email protected]/node_modules/puppeteer-core/src/node/BrowserLauncher.ts:100:24
❯ Module.launchPage tests/ai/web/puppeteer/utils.ts:12:19
❯ tests/ai/web/puppeteer/showcase.test.ts:36:37
|
tests/ai/web/puppeteer/showcase.test.ts > puppeteer integration > find widgets in antd:
packages/web-integration/tests/ai/web/puppeteer/utils.ts#L12
Error: Could not find Chrome (ver. 127.0.6533.99). This can occur if either
1. you did not perform an installation before running the script (e.g. `npx puppeteer browsers install chrome`) or
2. your cache path is incorrectly configured (which is: /home/runner/.cache/puppeteer).
For (2), check out our guide on configuring puppeteer at https://pptr.dev/guides/configuration.
❯ ChromeLauncher.resolveExecutablePath ../../node_modules/.pnpm/[email protected]/node_modules/puppeteer-core/src/node/BrowserLauncher.ts:443:17
❯ ChromeLauncher.executablePath ../../node_modules/.pnpm/[email protected]/node_modules/puppeteer-core/src/node/ChromeLauncher.ts:280:19
❯ ChromeLauncher.computeLaunchArguments ../../node_modules/.pnpm/[email protected]/node_modules/puppeteer-core/src/node/ChromeLauncher.ts:130:31
❯ ChromeLauncher.launch ../../node_modules/.pnpm/[email protected]/node_modules/puppeteer-core/src/node/BrowserLauncher.ts:100:24
❯ Module.launchPage tests/ai/web/puppeteer/utils.ts:12:19
❯ tests/ai/web/puppeteer/showcase.test.ts:57:37
|
tests/ai/evaluate/inspect.test.ts > aweme_play-1: inspect element:
packages/midscene/tests/ai/evaluate/inspect.test.ts#L91
AssertionError: expected 85.71428571428571 to be greater than 95
❯ test.timeout tests/ai/evaluate/inspect.test.ts:91:36
|
tests/ai/evaluate/inspect.test.ts > aweme_play-2: inspect element:
packages/midscene/tests/ai/evaluate/inspect.test.ts#L91
AssertionError: expected 85.71428571428571 to be greater than 95
❯ test.timeout tests/ai/evaluate/inspect.test.ts:91:36
|
main (18.19.0)
The following actions use a deprecated Node.js version and will be forced to run on node20: pnpm/action-setup@v2, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|