Skip to content

chore(deps): bump vite from 5.4.2 to 5.4.11 #7140

chore(deps): bump vite from 5.4.2 to 5.4.11

chore(deps): bump vite from 5.4.2 to 5.4.11 #7140

Triggered via pull request November 20, 2024 18:54
Status Failure
Total duration 5m 8s
Artifacts 1

playwright.yml

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

Annotations

21 errors, 27 warnings, and 10 notices
[chromium] › specs/onboarding/onboarding.spec.ts:14:3 › Onboarding an existing user › going through the onboarding flow to sign in: tests/page-object-models/onboarding.page.ts#L273
1) [chromium] › specs/onboarding/onboarding.spec.ts:14:3 › Onboarding an existing user › going through the onboarding flow to sign in Error: No key found at page-object-models/onboarding.page.ts:273 271 | async enterMnemonicKey(secretKey: string) { 272 | // NOTE: TEST_ACCOUNT_SECRET_KEY needs to be obtained and set in .env > 273 | if (!secretKey) throw new Error('No key found'); | ^ 274 | const key = secretKey.split(' '); 275 | for (let i = 0; i < key.length; i++) { 276 | await this.page.getByTestId(`mnemonic-input-${i + 1}`).fill(key[i]); at OnboardingPage.enterMnemonicKey (/home/runner/work/extension/extension/tests/page-object-models/onboarding.page.ts:273:27) at OnboardingPage.signInExistingUser (/home/runner/work/extension/extension/tests/page-object-models/onboarding.page.ts:260:16) at /home/runner/work/extension/extension/tests/specs/onboarding/onboarding.spec.ts:21:5
[chromium] › specs/onboarding/onboarding.spec.ts:14:3 › Onboarding an existing user › going through the onboarding flow to sign in: tests/page-object-models/onboarding.page.ts#L273
1) [chromium] › specs/onboarding/onboarding.spec.ts:14:3 › Onboarding an existing user › going through the onboarding flow to sign in Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: No key found at page-object-models/onboarding.page.ts:273 271 | async enterMnemonicKey(secretKey: string) { 272 | // NOTE: TEST_ACCOUNT_SECRET_KEY needs to be obtained and set in .env > 273 | if (!secretKey) throw new Error('No key found'); | ^ 274 | const key = secretKey.split(' '); 275 | for (let i = 0; i < key.length; i++) { 276 | await this.page.getByTestId(`mnemonic-input-${i + 1}`).fill(key[i]); at OnboardingPage.enterMnemonicKey (/home/runner/work/extension/extension/tests/page-object-models/onboarding.page.ts:273:27) at OnboardingPage.signInExistingUser (/home/runner/work/extension/extension/tests/page-object-models/onboarding.page.ts:260:16) at /home/runner/work/extension/extension/tests/specs/onboarding/onboarding.spec.ts:21:5
[chromium] › specs/onboarding/onboarding.spec.ts:14:3 › Onboarding an existing user › going through the onboarding flow to sign in: tests/page-object-models/onboarding.page.ts#L273
1) [chromium] › specs/onboarding/onboarding.spec.ts:14:3 › Onboarding an existing user › going through the onboarding flow to sign in Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── Error: No key found at page-object-models/onboarding.page.ts:273 271 | async enterMnemonicKey(secretKey: string) { 272 | // NOTE: TEST_ACCOUNT_SECRET_KEY needs to be obtained and set in .env > 273 | if (!secretKey) throw new Error('No key found'); | ^ 274 | const key = secretKey.split(' '); 275 | for (let i = 0; i < key.length; i++) { 276 | await this.page.getByTestId(`mnemonic-input-${i + 1}`).fill(key[i]); at OnboardingPage.enterMnemonicKey (/home/runner/work/extension/extension/tests/page-object-models/onboarding.page.ts:273:27) at OnboardingPage.signInExistingUser (/home/runner/work/extension/extension/tests/page-object-models/onboarding.page.ts:260:16) at /home/runner/work/extension/extension/tests/specs/onboarding/onboarding.spec.ts:21:5
[chromium] › specs/onboarding/onboarding.spec.ts:86:7 › Onboarding an existing user › Address generation › Bitcoin › that the wallet generates the correct Native Segwit address: tests/page-object-models/onboarding.page.ts#L273
2) [chromium] › specs/onboarding/onboarding.spec.ts:86:7 › Onboarding an existing user › Address generation › Bitcoin › that the wallet generates the correct Native Segwit address Error: No key found at page-object-models/onboarding.page.ts:273 271 | async enterMnemonicKey(secretKey: string) { 272 | // NOTE: TEST_ACCOUNT_SECRET_KEY needs to be obtained and set in .env > 273 | if (!secretKey) throw new Error('No key found'); | ^ 274 | const key = secretKey.split(' '); 275 | for (let i = 0; i < key.length; i++) { 276 | await this.page.getByTestId(`mnemonic-input-${i + 1}`).fill(key[i]); at OnboardingPage.enterMnemonicKey (/home/runner/work/extension/extension/tests/page-object-models/onboarding.page.ts:273:27) at OnboardingPage.signInExistingUser (/home/runner/work/extension/extension/tests/page-object-models/onboarding.page.ts:260:16) at /home/runner/work/extension/extension/tests/specs/onboarding/onboarding.spec.ts:82:7
[chromium] › specs/onboarding/onboarding.spec.ts:86:7 › Onboarding an existing user › Address generation › Bitcoin › that the wallet generates the correct Native Segwit address: tests/page-object-models/onboarding.page.ts#L273
2) [chromium] › specs/onboarding/onboarding.spec.ts:86:7 › Onboarding an existing user › Address generation › Bitcoin › that the wallet generates the correct Native Segwit address Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: No key found at page-object-models/onboarding.page.ts:273 271 | async enterMnemonicKey(secretKey: string) { 272 | // NOTE: TEST_ACCOUNT_SECRET_KEY needs to be obtained and set in .env > 273 | if (!secretKey) throw new Error('No key found'); | ^ 274 | const key = secretKey.split(' '); 275 | for (let i = 0; i < key.length; i++) { 276 | await this.page.getByTestId(`mnemonic-input-${i + 1}`).fill(key[i]); at OnboardingPage.enterMnemonicKey (/home/runner/work/extension/extension/tests/page-object-models/onboarding.page.ts:273:27) at OnboardingPage.signInExistingUser (/home/runner/work/extension/extension/tests/page-object-models/onboarding.page.ts:260:16) at /home/runner/work/extension/extension/tests/specs/onboarding/onboarding.spec.ts:82:7
[chromium] › specs/onboarding/onboarding.spec.ts:86:7 › Onboarding an existing user › Address generation › Bitcoin › that the wallet generates the correct Native Segwit address: tests/page-object-models/onboarding.page.ts#L273
2) [chromium] › specs/onboarding/onboarding.spec.ts:86:7 › Onboarding an existing user › Address generation › Bitcoin › that the wallet generates the correct Native Segwit address Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── Error: No key found at page-object-models/onboarding.page.ts:273 271 | async enterMnemonicKey(secretKey: string) { 272 | // NOTE: TEST_ACCOUNT_SECRET_KEY needs to be obtained and set in .env > 273 | if (!secretKey) throw new Error('No key found'); | ^ 274 | const key = secretKey.split(' '); 275 | for (let i = 0; i < key.length; i++) { 276 | await this.page.getByTestId(`mnemonic-input-${i + 1}`).fill(key[i]); at OnboardingPage.enterMnemonicKey (/home/runner/work/extension/extension/tests/page-object-models/onboarding.page.ts:273:27) at OnboardingPage.signInExistingUser (/home/runner/work/extension/extension/tests/page-object-models/onboarding.page.ts:260:16) at /home/runner/work/extension/extension/tests/specs/onboarding/onboarding.spec.ts:82:7
[chromium] › specs/onboarding/onboarding.spec.ts:91:7 › Onboarding an existing user › Address generation › Bitcoin › that the wallet generates the correct Taproot address: tests/page-object-models/onboarding.page.ts#L273
3) [chromium] › specs/onboarding/onboarding.spec.ts:91:7 › Onboarding an existing user › Address generation › Bitcoin › that the wallet generates the correct Taproot address Error: No key found at page-object-models/onboarding.page.ts:273 271 | async enterMnemonicKey(secretKey: string) { 272 | // NOTE: TEST_ACCOUNT_SECRET_KEY needs to be obtained and set in .env > 273 | if (!secretKey) throw new Error('No key found'); | ^ 274 | const key = secretKey.split(' '); 275 | for (let i = 0; i < key.length; i++) { 276 | await this.page.getByTestId(`mnemonic-input-${i + 1}`).fill(key[i]); at OnboardingPage.enterMnemonicKey (/home/runner/work/extension/extension/tests/page-object-models/onboarding.page.ts:273:27) at OnboardingPage.signInExistingUser (/home/runner/work/extension/extension/tests/page-object-models/onboarding.page.ts:260:16) at /home/runner/work/extension/extension/tests/specs/onboarding/onboarding.spec.ts:82:7
[chromium] › specs/onboarding/onboarding.spec.ts:91:7 › Onboarding an existing user › Address generation › Bitcoin › that the wallet generates the correct Taproot address: tests/page-object-models/onboarding.page.ts#L273
3) [chromium] › specs/onboarding/onboarding.spec.ts:91:7 › Onboarding an existing user › Address generation › Bitcoin › that the wallet generates the correct Taproot address Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: No key found at page-object-models/onboarding.page.ts:273 271 | async enterMnemonicKey(secretKey: string) { 272 | // NOTE: TEST_ACCOUNT_SECRET_KEY needs to be obtained and set in .env > 273 | if (!secretKey) throw new Error('No key found'); | ^ 274 | const key = secretKey.split(' '); 275 | for (let i = 0; i < key.length; i++) { 276 | await this.page.getByTestId(`mnemonic-input-${i + 1}`).fill(key[i]); at OnboardingPage.enterMnemonicKey (/home/runner/work/extension/extension/tests/page-object-models/onboarding.page.ts:273:27) at OnboardingPage.signInExistingUser (/home/runner/work/extension/extension/tests/page-object-models/onboarding.page.ts:260:16) at /home/runner/work/extension/extension/tests/specs/onboarding/onboarding.spec.ts:82:7
[chromium] › specs/onboarding/onboarding.spec.ts:91:7 › Onboarding an existing user › Address generation › Bitcoin › that the wallet generates the correct Taproot address: tests/page-object-models/onboarding.page.ts#L273
3) [chromium] › specs/onboarding/onboarding.spec.ts:91:7 › Onboarding an existing user › Address generation › Bitcoin › that the wallet generates the correct Taproot address Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── Error: No key found at page-object-models/onboarding.page.ts:273 271 | async enterMnemonicKey(secretKey: string) { 272 | // NOTE: TEST_ACCOUNT_SECRET_KEY needs to be obtained and set in .env > 273 | if (!secretKey) throw new Error('No key found'); | ^ 274 | const key = secretKey.split(' '); 275 | for (let i = 0; i < key.length; i++) { 276 | await this.page.getByTestId(`mnemonic-input-${i + 1}`).fill(key[i]); at OnboardingPage.enterMnemonicKey (/home/runner/work/extension/extension/tests/page-object-models/onboarding.page.ts:273:27) at OnboardingPage.signInExistingUser (/home/runner/work/extension/extension/tests/page-object-models/onboarding.page.ts:260:16) at /home/runner/work/extension/extension/tests/specs/onboarding/onboarding.spec.ts:82:7
[chromium] › specs/onboarding/onboarding.spec.ts:98:7 › Onboarding an existing user › Address generation › Stacks › that restoring a wallet generates the correct stacks address: tests/page-object-models/onboarding.page.ts#L273
4) [chromium] › specs/onboarding/onboarding.spec.ts:98:7 › Onboarding an existing user › Address generation › Stacks › that restoring a wallet generates the correct stacks address Error: No key found at page-object-models/onboarding.page.ts:273 271 | async enterMnemonicKey(secretKey: string) { 272 | // NOTE: TEST_ACCOUNT_SECRET_KEY needs to be obtained and set in .env > 273 | if (!secretKey) throw new Error('No key found'); | ^ 274 | const key = secretKey.split(' '); 275 | for (let i = 0; i < key.length; i++) { 276 | await this.page.getByTestId(`mnemonic-input-${i + 1}`).fill(key[i]); at OnboardingPage.enterMnemonicKey (/home/runner/work/extension/extension/tests/page-object-models/onboarding.page.ts:273:27) at OnboardingPage.signInExistingUser (/home/runner/work/extension/extension/tests/page-object-models/onboarding.page.ts:260:16) at /home/runner/work/extension/extension/tests/specs/onboarding/onboarding.spec.ts:82:7
[chromium] › specs/receive/receive.spec.ts:10:3 › Receive Dialog › That the Receive dialog renders and shows the correct assets: tests/page-object-models/onboarding.page.ts#L273
1) [chromium] › specs/receive/receive.spec.ts:10:3 › Receive Dialog › That the Receive dialog renders and shows the correct assets Error: No key found at page-object-models/onboarding.page.ts:273 271 | async enterMnemonicKey(secretKey: string) { 272 | // NOTE: TEST_ACCOUNT_SECRET_KEY needs to be obtained and set in .env > 273 | if (!secretKey) throw new Error('No key found'); | ^ 274 | const key = secretKey.split(' '); 275 | for (let i = 0; i < key.length; i++) { 276 | await this.page.getByTestId(`mnemonic-input-${i + 1}`).fill(key[i]); at OnboardingPage.enterMnemonicKey (/home/runner/work/extension/extension/tests/page-object-models/onboarding.page.ts:273:27) at OnboardingPage.signInExistingUser (/home/runner/work/extension/extension/tests/page-object-models/onboarding.page.ts:260:16) at /home/runner/work/extension/extension/tests/specs/receive/receive.spec.ts:6:5
[chromium] › specs/receive/receive.spec.ts:10:3 › Receive Dialog › That the Receive dialog renders and shows the correct assets: tests/page-object-models/onboarding.page.ts#L273
1) [chromium] › specs/receive/receive.spec.ts:10:3 › Receive Dialog › That the Receive dialog renders and shows the correct assets Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: No key found at page-object-models/onboarding.page.ts:273 271 | async enterMnemonicKey(secretKey: string) { 272 | // NOTE: TEST_ACCOUNT_SECRET_KEY needs to be obtained and set in .env > 273 | if (!secretKey) throw new Error('No key found'); | ^ 274 | const key = secretKey.split(' '); 275 | for (let i = 0; i < key.length; i++) { 276 | await this.page.getByTestId(`mnemonic-input-${i + 1}`).fill(key[i]); at OnboardingPage.enterMnemonicKey (/home/runner/work/extension/extension/tests/page-object-models/onboarding.page.ts:273:27) at OnboardingPage.signInExistingUser (/home/runner/work/extension/extension/tests/page-object-models/onboarding.page.ts:260:16) at /home/runner/work/extension/extension/tests/specs/receive/receive.spec.ts:6:5
[chromium] › specs/receive/receive.spec.ts:10:3 › Receive Dialog › That the Receive dialog renders and shows the correct assets: tests/page-object-models/onboarding.page.ts#L273
1) [chromium] › specs/receive/receive.spec.ts:10:3 › Receive Dialog › That the Receive dialog renders and shows the correct assets Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── Error: No key found at page-object-models/onboarding.page.ts:273 271 | async enterMnemonicKey(secretKey: string) { 272 | // NOTE: TEST_ACCOUNT_SECRET_KEY needs to be obtained and set in .env > 273 | if (!secretKey) throw new Error('No key found'); | ^ 274 | const key = secretKey.split(' '); 275 | for (let i = 0; i < key.length; i++) { 276 | await this.page.getByTestId(`mnemonic-input-${i + 1}`).fill(key[i]); at OnboardingPage.enterMnemonicKey (/home/runner/work/extension/extension/tests/page-object-models/onboarding.page.ts:273:27) at OnboardingPage.signInExistingUser (/home/runner/work/extension/extension/tests/page-object-models/onboarding.page.ts:260:16) at /home/runner/work/extension/extension/tests/specs/receive/receive.spec.ts:6: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
2) [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
2) [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: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
Shard 5 of 10
Process completed with exit code 1.
Merge reports
Action failed with "not found deploy key or tokens"
Merge reports
Action failed with "not found deploy key or tokens"
Merge reports
Process returned exit code 1 Launched as "/home/runner/runners/2.320.0/externals/node20/bin/node /home/runner/work/_actions/Wandalen/wretry.action/v3.7.3_js_action/src/Runner.mjs /home/runner/work/_actions/Wandalen/actions-gh-pages/lib/index.js" Launched at "/home/runner/work/extension/extension" Attempts exhausted, made 2 attempts : Attempt #1 started at : 18:59:40 GMT+0000 (Coordinated Universal Time) Attempt #2 started at : 18:59:40 GMT+0000 (Coordinated Universal Time)
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.4s
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 16.4s
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/profile/profile.spec.ts#L1
[chromium] › specs/profile/profile.spec.ts took 22.7s
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 39.0s
Slow Test: [chromium] › specs/rpc-open/open.spec.ts#L1
[chromium] › specs/rpc-open/open.spec.ts took 19.2s
Slow Test: [chromium] › specs/rpc-stacks-transaction/transaction-signing.spec.ts#L1
[chromium] › specs/rpc-stacks-transaction/transaction-signing.spec.ts took 16.4s
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 15.6s
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 48.6s
Slow Test: [chromium] › specs/send/send-inscription.spec.ts#L1
[chromium] › specs/send/send-inscription.spec.ts took 37.0s
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/ledger/ledger.spec.ts#L1
[chromium] › specs/ledger/ledger.spec.ts took 47.5s
Slow Test: [chromium] › specs/compliance-checks/compliance-checks.spec.ts#L1
[chromium] › specs/compliance-checks/compliance-checks.spec.ts took 24.7s
Slow Test: [chromium] › specs/fund/fund.spec.ts#L1
[chromium] › specs/fund/fund.spec.ts took 15.3s
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/
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
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
6 passed (47.7s)
🎭 Playwright Run Summary
1 skipped 3 passed (36.9s)
🎭 Playwright Run Summary
4 passed (35.4s)
🎭 Playwright Run Summary
4 failed [chromium] › specs/onboarding/onboarding.spec.ts:14:3 › Onboarding an existing user › going through the onboarding flow to sign in [chromium] › specs/onboarding/onboarding.spec.ts:86:7 › Onboarding an existing user › Address generation › Bitcoin › that the wallet generates the correct Native Segwit address [chromium] › specs/onboarding/onboarding.spec.ts:91:7 › Onboarding an existing user › Address generation › Bitcoin › that the wallet generates the correct Taproot address [chromium] › specs/onboarding/onboarding.spec.ts:98:7 › Onboarding an existing user › Address generation › Stacks › that restoring a wallet generates the correct stacks address 5 passed (1.6m)
🎭 Playwright Run Summary
9 passed (1.3m)
🎭 Playwright Run Summary
11 passed (1.4m)
🎭 Playwright Run Summary
11 passed (1.5m)
🎭 Playwright Run Summary
17 passed (1.6m)
🎭 Playwright Run Summary
1 failed [chromium] › specs/receive/receive.spec.ts:10:3 › Receive Dialog › That the Receive dialog renders and shows the correct assets 2 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:103:7 › Rpc: GetAddresses › ledgerWithStacksKeysOnly › the promise resolves with addresses successfully 8 passed (2.5m)
🎭 Playwright Run Summary
17 passed (2.2m)

Artifacts

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