Skip to content

Use mudder to rank form elements and related pub values #2320

Use mudder to rank form elements and related pub values

Use mudder to rank form elements and related pub values #2320

Triggered via pull request March 4, 2025 15:08
Status Success
Total duration 15m 32s
Artifacts 3

on_pr.yml

on: pull_request
ci  /  ci
2m 50s
ci / ci
build-all  /  Emit container tag sha
6s
build-all / Emit container tag sha
build-all  /  ...  /  Build
2m 54s
build-all / build-base / Build
build-all  /  ...  /  Build
4m 50s
build-all / build-core / Build
build-all  /  ...  /  Build
1m 40s
build-all / build-jobs / Build
Fit to window
Zoom out
Zoom in

Annotations

2 errors, 27 warnings, and 1 notice
[chromium] › formBuilder.spec.ts:247:2 › reordering fields › field order is persisted after saving: core/playwright/formBuilder.spec.ts#L264
1) [chromium] › formBuilder.spec.ts:247:2 › reordering fields › field order is persisted after saving Error: Timed out 5000ms waiting for expect(locator).not.toHaveText(expected) Locator: getByRole('button', { name: /(Paragraph|playwright-test-community-1741101682821).*/ }) Expected: not ["Paragraph:value{field=\"title\"}", "playwright-test-community-1741101682821:titleTitle", "playwright-test-community-1741101682821:contentContent"] Received: ["Paragraph:value{field=\"title\"}", "playwright-test-community-1741101682821:titleTitle", "playwright-test-community-1741101682821:contentContent"] Call log: - expect.not.toHaveText with timeout 5000ms - waiting for getByRole('button', { name: /(Paragraph|playwright-test-community-1741101682821).*/ }) - locator resolved to 3 elements - locator resolved to 3 elements - locator resolved to 3 elements - locator resolved to 3 elements - locator resolved to 3 elements - locator resolved to 3 elements - locator resolved to 3 elements - locator resolved to 3 elements - locator resolved to 3 elements 262 | 263 | // Make sure reordering worked on the client > 264 | expect(changedElements).not.toHaveText(initialElements); | ^ 265 | 266 | await formEditPage.saveForm(); 267 | at /home/runner/work/platform/platform/core/playwright/formBuilder.spec.ts:264:31
[chromium] › formBuilder.spec.ts:247:2 › reordering fields › field order is persisted after saving: core/playwright/fixtures/forms-edit-page.ts#L37
1) [chromium] › formBuilder.spec.ts:247:2 › reordering fields › field order is persisted after saving Error: locator.click: Target page, context or browser has been closed Call log: - waiting for getByTestId('save-form-button') - locator resolved to <button disabled type="submit" form="formbuilderform" data-testid="save-form-button" class="items-center justify-center whitespace-nowrap text-sm font-medium transition-colors focus-visible:outline-none focus-visible:ring-1 focus-visible:ring-gray-950 disabled:pointer-events-none disabled:opacity-50 dark:focus-visible:ring-gray-300 [&_svg]:pointer-events-none [&_svg]:size-4 [&_svg]:shrink-0 text-gray-50 shadow hover:bg-gray-900/90 dark:bg-gray-50 dark:text-gray-900 dark:hover:bg-gray-50/90 h-10 rounde…>Save</button> - attempting click action - waiting for element to be visible, enabled and stable - element is not enabled - retrying click action, attempt #1 - waiting for element to be visible, enabled and stable - element is not enabled - retrying click action, attempt #2 - waiting 20ms - waiting for element to be visible, enabled and stable - element is not enabled - retrying click action, attempt #3 - waiting 100ms - waiting for element to be visible, enabled and stable - element is not enabled - retrying click action, attempt #4 - waiting 100ms - waiting for element to be visible, enabled and stable - element is not enabled - retrying click action, attempt #5 - waiting 500ms - waiting for element to be visible, enabled and stable - element is not enabled - retrying click action, attempt #6 - waiting 500ms - waiting for element to be visible, enabled and stable - element is not enabled - retrying click action, attempt #7 - waiting 500ms - waiting for element to be visible, enabled and stable - element is not enabled - retrying click action, attempt #8 - waiting 500ms - waiting for element to be visible, enabled and stable - element is not enabled - retrying click action, attempt #9 - waiting 500ms - waiting for element to be visible, enabled and stable - element is not enabled - retrying click action, attempt #10 - waiting 500ms - waiting for element to be visible, enabled and stable - element is not enabled - retrying click action, attempt #11 - waiting 500ms - waiting for element to be visible, enabled and stable - element is not enabled - retrying click action, attempt #12 - waiting 500ms - waiting for element to be visible, enabled and stable - element is not enabled - retrying click action, attempt #13 - waiting 500ms - waiting for element to be visible, enabled and stable - element is not enabled - retrying click action, attempt #14 - waiting 500ms at fixtures/forms-edit-page.ts:37 35 | 36 | async saveForm() { > 37 | await this.page.getByTestId("save-form-button").click(); | ^ 38 | await this.page.getByText("Form Successfully Saved", { exact: true }).waitFor(); 39 | } 40 | } at FormsEditPage.saveForm (/home/runner/work/platform/platform/core/playwright/fixtures/forms-edit-page.ts:37:51) at /home/runner/work/platform/platform/core/playwright/formBuilder.spec.ts:266:22
The 'as' keyword should match the case of the 'from' keyword: Dockerfile#L18
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
The 'as' keyword should match the case of the 'from' keyword: Dockerfile#L42
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
The 'as' keyword should match the case of the 'from' keyword: Dockerfile#L57
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
The 'as' keyword should match the case of the 'from' keyword: Dockerfile#L84
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
The 'as' keyword should match the case of the 'from' keyword: Dockerfile#L91
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
The 'as' keyword should match the case of the 'from' keyword: Dockerfile#L107
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
Legacy key/value format with whitespace separator should not be used: Dockerfile#L79
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals: Dockerfile#L99
JSONArgsRecommended: JSON arguments recommended for CMD to prevent unintended behavior related to OS signals More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/
The 'as' keyword should match the case of the 'from' keyword: Dockerfile#L18
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
The 'as' keyword should match the case of the 'from' keyword: Dockerfile#L42
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
The 'as' keyword should match the case of the 'from' keyword: Dockerfile#L57
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
The 'as' keyword should match the case of the 'from' keyword: Dockerfile#L84
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
The 'as' keyword should match the case of the 'from' keyword: Dockerfile#L91
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
The 'as' keyword should match the case of the 'from' keyword: Dockerfile#L107
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
The 'as' keyword should match the case of the 'from' keyword: Dockerfile#L18
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
The 'as' keyword should match the case of the 'from' keyword: Dockerfile#L42
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
The 'as' keyword should match the case of the 'from' keyword: Dockerfile#L84
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
The 'as' keyword should match the case of the 'from' keyword: Dockerfile#L107
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
JSON arguments recommended for ENTRYPOINT/CMD to prevent unintended behavior related to OS signals: Dockerfile#L135
JSONArgsRecommended: JSON arguments recommended for CMD to prevent unintended behavior related to OS signals More info: https://docs.docker.com/go/dockerfile/rule/json-args-recommended/
The 'as' keyword should match the case of the 'from' keyword: Dockerfile#L57
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
The 'as' keyword should match the case of the 'from' keyword: Dockerfile#L91
FromAsCasing: 'as' and 'FROM' keywords' casing do not match More info: https://docs.docker.com/go/dockerfile/rule/from-as-casing/
Legacy key/value format with whitespace separator should not be used: Dockerfile#L79
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: Dockerfile#L111
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: Dockerfile#L120
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Slow Test: core/[chromium] › pub.spec.ts#L1
core/[chromium] › pub.spec.ts took 36.0s
Slow Test: core/[chromium] › externalFormCreatePub.spec.ts#L1
core/[chromium] › externalFormCreatePub.spec.ts took 29.6s
Slow Test: core/[chromium] › fields.spec.ts#L1
core/[chromium] › fields.spec.ts took 21.9s
🎭 Playwright Run Summary
1 flaky [chromium] › formBuilder.spec.ts:247:2 › reordering fields › field order is persisted after saving 3 skipped 52 passed (5.4m)

Artifacts

Produced during runtime
Name Size
pubpub~platform~84DLAE.dockerbuild
59.2 KB
pubpub~platform~8W84M9.dockerbuild
59.6 KB
pubpub~platform~ZF06IG.dockerbuild
64.1 KB