Skip to content

[bot] ci: update npm packages #7162

[bot] ci: update npm packages

[bot] ci: update npm packages #7162

Triggered via pull request November 25, 2024 07:38
Status Success
Total duration 7m 5s
Artifacts 1

playwright.yml

on: pull_request
Matrix: test
Merge reports
21s
Merge reports
Fit to window
Zoom out
Zoom in

Annotations

13 errors, 26 warnings, and 10 notices
[chromium] › specs/ledger/ledger.spec.ts:60:7 › App with Ledger › withBitcoinAndStacksKey › that you can navigate to activity page: tests/specs/ledger/ledger.spec.ts#L1
1) [chromium] › specs/ledger/ledger.spec.ts:60:7 › App with Ledger › withBitcoinAndStacksKey › that you can navigate to activity page Test timeout of 30000ms exceeded.
[chromium] › specs/ledger/ledger.spec.ts:60:7 › App with Ledger › withBitcoinAndStacksKey › that you can navigate to activity page: tests/page-object-models/home.page.ts#L113
1) [chromium] › specs/ledger/ledger.spec.ts:60:7 › App with Ledger › withBitcoinAndStacksKey › that you can navigate to activity page Error: locator.click: Target page, context or browser has been closed Call log: - waiting for getByTestId('tab-activity') at page-object-models/home.page.ts:113 111 | 112 | async clickActivityTab() { > 113 | await this.page.getByTestId(HomePageSelectors.ActivityTabBtn).click(); | ^ 114 | } 115 | 116 | async clickSettingsButton() { at HomePage.clickActivityTab (/home/runner/work/extension/extension/tests/page-object-models/home.page.ts:113:67) at /home/runner/work/extension/extension/tests/specs/ledger/ledger.spec.ts:61:24
[chromium] › specs/profile/profile.spec.ts:19:3 › Profile updating › should show an error for invalid profile: tests/page-object-models/onboarding.page.ts#L303
1) [chromium] › specs/profile/profile.spec.ts:19:3 › Profile updating › should show an error for invalid profile Error: Unable to initialised wallet state at page-object-models/onboarding.page.ts:303 301 | 302 | do { > 303 | if (iterationCounter.getValue() > 5) throw new Error('Unable to initialised wallet state'); | ^ 304 | 305 | await this.page.evaluate( 306 | async walletState => chrome.storage.local.set({ 'persist:root': walletState }), at OnboardingPage.signInWithTestAccount (/home/runner/work/extension/extension/tests/page-object-models/onboarding.page.ts:303:50) at /home/runner/work/extension/extension/tests/specs/profile/profile.spec.ts:15:5
[chromium] › specs/rpc-get-addresses/get-addresses.spec.ts:103:7 › Rpc: GetAddresses › ledgerWithBitcoinAndStacksKey › the promise resolves with addresses successfully: tests/specs/rpc-get-addresses/get-addresses.spec.ts#L1
1) [chromium] › specs/rpc-get-addresses/get-addresses.spec.ts:103:7 › Rpc: GetAddresses › ledgerWithBitcoinAndStacksKey › the promise resolves with addresses successfully Test timeout of 30000ms exceeded.
[chromium] › specs/rpc-get-addresses/get-addresses.spec.ts:103:7 › Rpc: GetAddresses › ledgerWithBitcoinAndStacksKey › the promise resolves with addresses successfully: tests/specs/rpc-get-addresses/get-addresses.spec.ts#L104
1) [chromium] › specs/rpc-get-addresses/get-addresses.spec.ts:103:7 › Rpc: GetAddresses › ledgerWithBitcoinAndStacksKey › the promise resolves with addresses successfully Error: page.goto: Target page, context or browser has been closed Call log: - navigating to "localhost:3000", waiting until "load" 102 | 103 | test('the promise resolves with addresses successfully', async ({ page, context }) => { > 104 | await page.goto('localhost:3000'); | ^ 105 | const getAddressesPromise = initiateGetAddresses(page); 106 | 107 | const popup = await interceptRequestPopup(context); at /home/runner/work/extension/extension/tests/specs/rpc-get-addresses/get-addresses.spec.ts:104:20
[chromium] › specs/rpc-get-addresses/get-addresses.spec.ts:117:7 › Rpc: GetAddresses › ledgerWithBitcoinAndStacksKey › the promise rejects when user closes popup window: tests/specs/rpc-get-addresses/get-addresses.spec.ts#L1
2) [chromium] › specs/rpc-get-addresses/get-addresses.spec.ts:117:7 › Rpc: GetAddresses › ledgerWithBitcoinAndStacksKey › the promise rejects when user closes popup window Test timeout of 30000ms exceeded.
[chromium] › specs/rpc-get-addresses/get-addresses.spec.ts:117:7 › Rpc: GetAddresses › ledgerWithBitcoinAndStacksKey › the promise rejects when user closes popup window: tests/specs/rpc-get-addresses/get-addresses.spec.ts#L118
2) [chromium] › specs/rpc-get-addresses/get-addresses.spec.ts:117:7 › Rpc: GetAddresses › ledgerWithBitcoinAndStacksKey › the promise rejects when user closes popup window Error: page.goto: Target page, context or browser has been closed Call log: - navigating to "localhost:3000", waiting until "load" 116 | 117 | test('the promise rejects when user closes popup window', async ({ page, context }) => { > 118 | await page.goto('localhost:3000'); | ^ 119 | const getAddressesPromise = initiateGetAddresses(page); 120 | const popup = await interceptRequestPopup(context); 121 | await popup.close(); at /home/runner/work/extension/extension/tests/specs/rpc-get-addresses/get-addresses.spec.ts:118:20
[chromium] › specs/rpc-get-addresses/get-addresses.spec.ts:103:7 › Rpc: GetAddresses › ledgerWithStacksKeysOnly › the promise resolves with addresses successfully: tests/specs/rpc-get-addresses/get-addresses.spec.ts#L1
3) [chromium] › specs/rpc-get-addresses/get-addresses.spec.ts:103:7 › Rpc: GetAddresses › ledgerWithStacksKeysOnly › the promise resolves with addresses successfully Test timeout of 30000ms exceeded.
[chromium] › specs/rpc-get-addresses/get-addresses.spec.ts:103:7 › Rpc: GetAddresses › ledgerWithStacksKeysOnly › the promise resolves with addresses successfully: tests/specs/rpc-get-addresses/get-addresses.spec.ts#L104
3) [chromium] › specs/rpc-get-addresses/get-addresses.spec.ts:103:7 › Rpc: GetAddresses › ledgerWithStacksKeysOnly › the promise resolves with addresses successfully Error: page.goto: Target page, context or browser has been closed Call log: - navigating to "localhost:3000", waiting until "load" 102 | 103 | test('the promise resolves with addresses successfully', async ({ page, context }) => { > 104 | await page.goto('localhost:3000'); | ^ 105 | const getAddressesPromise = initiateGetAddresses(page); 106 | 107 | const popup = await interceptRequestPopup(context); at /home/runner/work/extension/extension/tests/specs/rpc-get-addresses/get-addresses.spec.ts:104:20
[chromium] › specs/rpc-get-addresses/get-addresses.spec.ts:117:7 › Rpc: GetAddresses › ledgerWithStacksKeysOnly › the promise rejects when user closes popup window: tests/specs/rpc-get-addresses/get-addresses.spec.ts#L1
4) [chromium] › specs/rpc-get-addresses/get-addresses.spec.ts:117:7 › Rpc: GetAddresses › ledgerWithStacksKeysOnly › the promise rejects when user closes popup window Test timeout of 30000ms exceeded.
[chromium] › specs/rpc-get-addresses/get-addresses.spec.ts:117:7 › Rpc: GetAddresses › ledgerWithStacksKeysOnly › the promise rejects when user closes popup window: tests/specs/rpc-get-addresses/get-addresses.spec.ts#L118
4) [chromium] › specs/rpc-get-addresses/get-addresses.spec.ts:117:7 › Rpc: GetAddresses › ledgerWithStacksKeysOnly › the promise rejects when user closes popup window Error: page.goto: Target page, context or browser has been closed Call log: - navigating to "localhost:3000", waiting until "load" 116 | 117 | test('the promise rejects when user closes popup window', async ({ page, context }) => { > 118 | await page.goto('localhost:3000'); | ^ 119 | const getAddressesPromise = initiateGetAddresses(page); 120 | const popup = await interceptRequestPopup(context); 121 | await popup.close(); at /home/runner/work/extension/extension/tests/specs/rpc-get-addresses/get-addresses.spec.ts:118:20
[chromium] › specs/rpc-get-addresses/get-addresses.spec.ts:103:7 › Rpc: GetAddresses › ledgerWithBitcoinKeysOnly › the promise resolves with addresses successfully: tests/specs/rpc-get-addresses/get-addresses.spec.ts#L1
5) [chromium] › specs/rpc-get-addresses/get-addresses.spec.ts:103:7 › Rpc: GetAddresses › ledgerWithBitcoinKeysOnly › the promise resolves with addresses successfully Test timeout of 30000ms exceeded.
[chromium] › specs/rpc-get-addresses/get-addresses.spec.ts:103:7 › Rpc: GetAddresses › ledgerWithBitcoinKeysOnly › the promise resolves with addresses successfully: tests/specs/rpc-get-addresses/get-addresses.spec.ts#L104
5) [chromium] › specs/rpc-get-addresses/get-addresses.spec.ts:103:7 › Rpc: GetAddresses › ledgerWithBitcoinKeysOnly › the promise resolves with addresses successfully Error: page.goto: Target page, context or browser has been closed Call log: - navigating to "localhost:3000", waiting until "load" 102 | 103 | test('the promise resolves with addresses successfully', async ({ page, context }) => { > 104 | await page.goto('localhost:3000'); | ^ 105 | const getAddressesPromise = initiateGetAddresses(page); 106 | 107 | const popup = await interceptRequestPopup(context); at /home/runner/work/extension/extension/tests/specs/rpc-get-addresses/get-addresses.spec.ts:104:20
Shard 2 of 10
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/upload-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Slow Test: [chromium] › specs/manage-transaction/manage-transaction.spec.ts#L1
[chromium] › specs/manage-transaction/manage-transaction.spec.ts took 15.8s
Shard 9 of 10
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/upload-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Slow Test: [chromium] › specs/settings/settings.spec.ts#L1
[chromium] › specs/settings/settings.spec.ts took 42.9s
Shard 10 of 10
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/upload-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Slow Test: [chromium] › specs/transactions/transactions.spec.ts#L1
[chromium] › specs/transactions/transactions.spec.ts took 25.8s
Shard 6 of 10
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/upload-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Slow Test: [chromium] › specs/rpc-sign-psbt/sign-psbt.spec.ts#L1
[chromium] › specs/rpc-sign-psbt/sign-psbt.spec.ts took 37.5s
Slow Test: [chromium] › specs/rpc-open/open.spec.ts#L1
[chromium] › specs/rpc-open/open.spec.ts took 19.5s
Slow Test: [chromium] › specs/rpc-stacks-transaction/transaction-signing.spec.ts#L1
[chromium] › specs/rpc-stacks-transaction/transaction-signing.spec.ts took 16.5s
Shard 7 of 10
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/upload-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Slow Test: [chromium] › specs/send/send-btc.spec.ts#L1
[chromium] › specs/send/send-btc.spec.ts took 49.0s
Slow Test: [chromium] › specs/send/send-inscription.spec.ts#L1
[chromium] › specs/send/send-inscription.spec.ts took 37.9s
Shard 3 of 10
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/upload-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Slow Test: [chromium] › specs/network/add-network.spec.ts#L1
[chromium] › specs/network/add-network.spec.ts took 1.1m
Slow Test: [chromium] › specs/message-signing/bip322-message-signing.spec.ts#L1
[chromium] › specs/message-signing/bip322-message-signing.spec.ts took 16.6s
Shard 1 of 10
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/upload-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Slow Test: [chromium] › specs/compliance-checks/compliance-checks.spec.ts#L1
[chromium] › specs/compliance-checks/compliance-checks.spec.ts took 24.3s
Slow Test: [chromium] › specs/fund/fund.spec.ts#L1
[chromium] › specs/fund/fund.spec.ts took 15.0s
Shard 8 of 10
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/upload-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Slow Test: [chromium] › specs/send/send-stx.spec.ts#L1
[chromium] › specs/send/send-stx.spec.ts took 2.0m
Shard 4 of 10
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/upload-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Slow Test: [chromium] › specs/onboarding/onboarding.spec.ts#L1
[chromium] › specs/onboarding/onboarding.spec.ts took 1.0m
Shard 5 of 10
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/upload-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Merge reports
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/download-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Deprecation notice: v1, v2, and v3 of the artifact actions
The following artifacts were uploaded using a version of actions/upload-artifact that is scheduled for deprecation: "all-blob-reports". Please update your workflow to use v4 of the artifact actions. Learn more: https://github.blog/changelog/2024-04-16-deprecation-notice-v3-of-the-artifact-actions/
🎭 Playwright Run Summary
4 passed (34.6s)
🎭 Playwright Run Summary
6 passed (47.8s)
🎭 Playwright Run Summary
1 skipped 3 passed (38.1s)
🎭 Playwright Run Summary
9 passed (1.3m)
🎭 Playwright Run Summary
11 passed (1.5m)
🎭 Playwright Run Summary
11 passed (1.4m)
🎭 Playwright Run Summary
1 flaky [chromium] › specs/ledger/ledger.spec.ts:60:7 › App with Ledger › withBitcoinAndStacksKey › that you can navigate to activity page 16 passed (2.2m)
🎭 Playwright Run Summary
17 passed (2.2m)
🎭 Playwright Run Summary
1 flaky [chromium] › specs/profile/profile.spec.ts:19:3 › Profile updating › should show an error for invalid profile 8 passed (1.9m)
🎭 Playwright Run Summary
5 flaky [chromium] › specs/rpc-get-addresses/get-addresses.spec.ts:103:7 › Rpc: GetAddresses › ledgerWithBitcoinAndStacksKey › the promise resolves with addresses successfully [chromium] › specs/rpc-get-addresses/get-addresses.spec.ts:117:7 › Rpc: GetAddresses › ledgerWithBitcoinAndStacksKey › the promise rejects when user closes popup window [chromium] › specs/rpc-get-addresses/get-addresses.spec.ts:103:7 › Rpc: GetAddresses › ledgerWithStacksKeysOnly › the promise resolves with addresses successfully [chromium] › specs/rpc-get-addresses/get-addresses.spec.ts:117:7 › Rpc: GetAddresses › ledgerWithStacksKeysOnly › the promise rejects when user closes popup window [chromium] › specs/rpc-get-addresses/get-addresses.spec.ts:103:7 › Rpc: GetAddresses › ledgerWithBitcoinKeysOnly › the promise resolves with addresses successfully 6 passed (4.2m)

Artifacts

Produced during runtime
Name Size
all-blob-reports Expired
10.6 MB