fix(bBottomSlide): replace await
with SyncPromise
when setting mo…
#6439
test.yml
on: push
Matrix: build
Matrix: linters
Matrix: components
Matrix: modules
Annotations
6 errors, 6 warnings, and 4 notices
[unit] › core/component/directives/attrs/test/unit/main.ts:72:7 › core/component/directives/attrs › should allow specifying directives:
src/core/component/directives/attrs/test/unit/main.ts#L1
1) [unit] › core/component/directives/attrs/test/unit/main.ts:72:7 › core/component/directives/attrs › should allow specifying directives, events, and attributes simultaneously › for non-functional components
Test timeout of 30000ms exceeded.
|
[unit] › core/component/directives/attrs/test/unit/main.ts:72:7 › core/component/directives/attrs › should allow specifying directives:
src/core/component/directives/attrs/test/unit/main.ts#L89
1) [unit] › core/component/directives/attrs/test/unit/main.ts:72:7 › core/component/directives/attrs › should allow specifying directives, events, and attributes simultaneously › for non-functional components
Error: Expected a promise to be resolved but it was rejected
Error: page.waitForFunction: Target closed
87 | await test.expect(component).toHaveCSS('margin-top', '10px');
88 |
> 89 | await test.expect(waitForWatcherCallsCount(page, component, 3)).toBeResolved();
| ^
90 | });
91 |
92 | test('for functional components', async ({page}) => {
at /home/runner/work/Client/Client/src/core/component/directives/attrs/test/unit/main.ts:89:68
|
[unit] › core/component/directives/attrs/test/unit/main.ts:72:7 › core/component/directives/attrs › should allow specifying directives:
src/core/component/directives/attrs/test/unit/main.ts#L1
1) [unit] › core/component/directives/attrs/test/unit/main.ts:72:7 › core/component/directives/attrs › should allow specifying directives, events, and attributes simultaneously › for non-functional components
Pending operations:
- page.waitForFunction at src/core/component/directives/attrs/test/helpers.ts:64:4
|
[unit] › components/directives/on-resize/test/unit/main.ts:120:7 › components/directives/on-resize › the handler should be called › when there is a change in padding or border of the element:
src/components/directives/on-resize/test/unit/main.ts#L1
1) [unit] › components/directives/on-resize/test/unit/main.ts:120:7 › components/directives/on-resize › the handler should be called › when there is a change in padding or border of the element, regardless of whether the element has a box-sizing value of "content-box" or "border-box
Test timeout of 30000ms exceeded.
|
[unit] › components/directives/on-resize/test/unit/main.ts:120:7 › components/directives/on-resize › the handler should be called › when there is a change in padding or border of the element:
src/components/directives/on-resize/test/unit/main.ts#L135
1) [unit] › components/directives/on-resize/test/unit/main.ts:120:7 › components/directives/on-resize › the handler should be called › when there is a change in padding or border of the element, regardless of whether the element has a box-sizing value of "content-box" or "border-box
Error: Expected a promise to be resolved but it was rejected
Error: page.waitForFunction: Target closed
133 | });
134 |
> 135 | await test.expect(waitForWatcherCallsCount(page, component, 3)).toBeResolved();
| ^
136 | }
137 | );
138 | });
at /home/runner/work/Client/Client/src/components/directives/on-resize/test/unit/main.ts:135:69
|
[unit] › components/directives/on-resize/test/unit/main.ts:120:7 › components/directives/on-resize › the handler should be called › when there is a change in padding or border of the element:
src/components/directives/on-resize/test/unit/main.ts#L1
1) [unit] › components/directives/on-resize/test/unit/main.ts:120:7 › components/directives/on-resize › the handler should be called › when there is a change in padding or border of the element, regardless of whether the element has a box-sizing value of "content-box" or "border-box
Pending operations:
- page.waitForFunction at src/components/directives/on-resize/test/unit/main.ts:225:5
|
build (20.x)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache/save@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
modules (20.x)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache/restore@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
components (20.x, 4, 4)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache/restore@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
components (20.x, 3, 4)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache/restore@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
components (20.x, 2, 4)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache/restore@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
components (20.x, 1, 4)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache/restore@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 flaky
[unit] › core/component/directives/attrs/test/unit/main.ts:72:7 › core/component/directives/attrs › should allow specifying directives, events, and attributes simultaneously › for non-functional components
1 skipped
313 passed (7.3m)
|
🎭 Playwright Run Summary
1 skipped
379 passed (7.6m)
|
🎭 Playwright Run Summary
1 flaky
[unit] › components/directives/on-resize/test/unit/main.ts:120:7 › components/directives/on-resize › the handler should be called › when there is a change in padding or border of the element, regardless of whether the element has a box-sizing value of "content-box" or "border-box
1 skipped
349 passed (7.7m)
|
🎭 Playwright Run Summary
352 passed (8.2m)
|