#bsq -- fix: handle missing location header in redirect error response #7725
+6
−0
Annotations
3 errors, 2 warnings, and 1 notice
|
Run playwright Tests:
tests/utils/page/actions.ts#L31
2) [default] › tests/request/multipart-boundary/multipart-boundary.spec.ts:109:7 › Multipart boundary preservation › should auto-generate boundary when none is specified in Content-Type header
TimeoutError: locator.click: Timeout 30000ms exceeded.
Call log:
- waiting for getByRole('button', { name: 'Discard All and Remove' })
- locator resolved to <button type="button">…</button>
- attempting click action
2 × waiting for element to be visible, enabled and stable
- element is not stable
- retrying click action
- waiting 20ms
2 × waiting for element to be visible, enabled and stable
- element is not stable
- retrying click action
- waiting 100ms
- waiting for element to be visible, enabled and stable
- element is not stable
- retrying click action
- waiting 500ms
- waiting for element to be visible, enabled and stable
- element was detached from the DOM, retrying
at tests/utils/page/actions.ts:31
29 | if (hasDiscardButton) {
30 | // Drafts modal - click "Discard All and Remove"
> 31 | await page.getByRole('button', { name: 'Discard All and Remove' }).click();
| ^
32 | } else {
33 | // Regular modal - click the submit button
34 | await page.locator('.bruno-modal-footer .submit').click();
at /home/runner/work/bruno/bruno/tests/utils/page/actions.ts:31:76
at closeAllCollections (/home/runner/work/bruno/bruno/tests/utils/page/actions.ts:13:3)
at /home/runner/work/bruno/bruno/tests/request/multipart-boundary/multipart-boundary.spec.ts:38:5
|
|
Run playwright Tests:
tests/request/multipart-boundary/multipart-boundary.spec.ts#L37
2) [default] › tests/request/multipart-boundary/multipart-boundary.spec.ts:109:7 › Multipart boundary preservation › should auto-generate boundary when none is specified in Content-Type header
"afterAll" hook timeout of 30000ms exceeded.
35 | });
36 |
> 37 | test.afterAll(async ({ page }) => {
| ^
38 | await closeAllCollections(page);
39 | });
40 |
at /home/runner/work/bruno/bruno/tests/request/multipart-boundary/multipart-boundary.spec.ts:37:8
|
|
Run playwright Tests:
tests/preferences/default-collection-location/default-collection-location.spec.js#L81
1) [default] › tests/preferences/default-collection-location/default-collection-location.spec.js:62:7 › Default Location Feature › Should use default location in Create Collection modal
Error: expect(received).toBe(expected) // Object.is equality
Expected: true
Received: false
79 |
80 | const inputValue = await collectionLocationInput.inputValue();
> 81 | expect(inputValue.endsWith(EXPECTED_PATH_SUFFIX)).toBe(true);
| ^
82 |
83 | // cancel the collection creation
84 | await page.locator('.bruno-modal').getByRole('button', { name: 'Cancel' }).click();
at /home/runner/work/bruno/bruno/tests/preferences/default-collection-location/default-collection-location.spec.js:81:55
|
|
Complete job
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Run playwright Tests:
[default] › tests/shortcuts/bound-actions.spec.ts#L0
[default] › tests/shortcuts/bound-actions.spec.ts took 7.8m
|
|
Run playwright Tests
2 flaky
[default] › tests/preferences/default-collection-location/default-collection-location.spec.js:62:7 › Default Location Feature › Should use default location in Create Collection modal
[default] › tests/request/multipart-boundary/multipart-boundary.spec.ts:109:7 › Multipart boundary preservation › should auto-generate boundary when none is specified in Content-Type header
7 skipped
431 passed (22.4m)
|
Loading