fix: insufficient funds in send max btc flow #7147
Annotations
8 errors, 28 warnings, and 10 notices
[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 › ledgerWithBitcoinKeysOnly › 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 › 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
1) [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
|
[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#L71
1) [chromium] › specs/rpc-get-addresses/get-addresses.spec.ts:103:7 › Rpc: GetAddresses › ledgerWithBitcoinKeysOnly › the promise resolves with addresses successfully
Retry #1 ───────────────────────────────────────────────────────────────────────────────────────
Error: Timed out 5000ms waiting for expect(locator).toBeVisible()
Locator: getByTestId('get-addresses-approve-button')
Expected: visible
Received: <element(s) not found>
Call log:
- expect.toBeVisible with timeout 5000ms
- waiting for getByTestId('get-addresses-approve-button')
69 | async function clickConnectLeatherButton(popup: Page) {
70 | const button = popup.getByTestId('get-addresses-approve-button');
> 71 | await test.expect(button).toBeVisible();
| ^
72 | await button.click();
73 | }
74 |
at clickConnectLeatherButton (/home/runner/work/extension/extension/tests/specs/rpc-get-addresses/get-addresses.spec.ts:71:29)
at /home/runner/work/extension/extension/tests/specs/rpc-get-addresses/get-addresses.spec.ts:108:15
|
[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#L66
1) [chromium] › specs/rpc-get-addresses/get-addresses.spec.ts:103:7 › Rpc: GetAddresses › ledgerWithBitcoinKeysOnly › the promise resolves with addresses successfully
Retry #1 ───────────────────────────────────────────────────────────────────────────────────────
Error: page.evaluate: Target page, context or browser has been closed
64 |
65 | async function initiateGetAddresses(page: Page) {
> 66 | return page.evaluate(async () => (window as any).LeatherProvider?.request('getAddresses'));
| ^
67 | }
68 |
69 | async function clickConnectLeatherButton(popup: Page) {
at initiateGetAddresses (/home/runner/work/extension/extension/tests/specs/rpc-get-addresses/get-addresses.spec.ts:66:15)
at /home/runner/work/extension/extension/tests/specs/rpc-get-addresses/get-addresses.spec.ts:105:37
|
[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
1) [chromium] › specs/rpc-get-addresses/get-addresses.spec.ts:103:7 › Rpc: GetAddresses › ledgerWithBitcoinKeysOnly › the promise resolves with addresses successfully
Retry #2 ───────────────────────────────────────────────────────────────────────────────────────
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
1) [chromium] › specs/rpc-get-addresses/get-addresses.spec.ts:103:7 › Rpc: GetAddresses › ledgerWithBitcoinKeysOnly › the promise resolves with addresses successfully
Retry #2 ───────────────────────────────────────────────────────────────────────────────────────
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.
|
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 23.8s
|
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-tokens/manage-tokens.spec.ts#L1
[chromium] › specs/manage-tokens/manage-tokens.spec.ts took 18.1s
|
Slow Test:
[chromium] › specs/manage-transaction/manage-transaction.spec.ts#L1
[chromium] › specs/manage-transaction/manage-transaction.spec.ts took 16.3s
|
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 41.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/ledger/ledger.spec.ts#L1
[chromium] › specs/ledger/ledger.spec.ts took 47.4s
|
Slow Test:
[chromium] › specs/compliance-checks/compliance-checks.spec.ts#L1
[chromium] › specs/compliance-checks/compliance-checks.spec.ts took 25.0s
|
Slow Test:
[chromium] › specs/fund/fund.spec.ts#L1
[chromium] › specs/fund/fund.spec.ts took 15.3s
|
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.8s
|
Slow Test:
[chromium] › specs/send/send-inscription.spec.ts#L1
[chromium] › specs/send/send-inscription.spec.ts took 39.0s
|
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 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 38.0s
|
Slow Test:
[chromium] › specs/rpc-open/open.spec.ts#L1
[chromium] › specs/rpc-open/open.spec.ts took 19.3s
|
Slow Test:
[chromium] › specs/rpc-stacks-transaction/transaction-signing.spec.ts#L1
[chromium] › specs/rpc-stacks-transaction/transaction-signing.spec.ts took 17.2s
|
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
|
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/
|
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/
|
🎭 Playwright Run Summary
1 skipped
3 passed (35.4s)
|
🎭 Playwright Run Summary
4 passed (39.4s)
|
🎭 Playwright Run Summary
6 passed (46.7s)
|
🎭 Playwright Run Summary
11 passed (1.4m)
|
🎭 Playwright Run Summary
17 passed (1.7m)
|
🎭 Playwright Run Summary
11 passed (1.5m)
|
🎭 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
9 passed (1.3m)
|
🎭 Playwright Run Summary
1 failed
[chromium] › specs/rpc-get-addresses/get-addresses.spec.ts:103:7 › Rpc: GetAddresses › ledgerWithBitcoinKeysOnly › the promise resolves with addresses successfully
10 passed (2.5m)
|
🎭 Playwright Run Summary
17 passed (2.2m)
|
Artifacts
Produced during runtime
Name | Size | |
---|---|---|
all-blob-reports
Expired
|
5.31 MB |
|