Skip to content

front: fix flaky e2e tests #10816

front: fix flaky e2e tests

front: fix flaky e2e tests #10816

Re-run triggered September 11, 2024 09:02
Status Success
Total duration 8m 41s
Artifacts 4

build.yml

on: pull_request
Matrix: build
check_generated_railjson_sync
27s
check_generated_railjson_sync
check_railjson_generator
1m 54s
check_railjson_generator
check_commits
5s
check_commits
Check final newline
9s
Check final newline
check_integration_tests
1m 20s
check_integration_tests
check_osrd_schema
44s
check_osrd_schema
check_toml
5s
check_toml
check_infra_schema_sync
13s
check_infra_schema_sync
check_reuse_compliance
8s
check_reuse_compliance
Fit to window
Zoom out
Zoom in

Annotations

7 errors, 15 warnings, and 1 notice
[firefox] › 003-study-management.spec.ts:29:7 › Test if operationnal study: study creation workflow is working properly › Create a new study: tests/003-study-management.spec.ts#L1
1) [firefox] › 003-study-management.spec.ts:29:7 › Test if operationnal study: study creation workflow is working properly › Create a new study Test timeout of 60000ms exceeded.
[firefox] › 003-study-management.spec.ts:29:7 › Test if operationnal study: study creation workflow is working properly › Create a new study: tests/pages/study-page-model.ts#L118
1) [firefox] › 003-study-management.spec.ts:29:7 › Test if operationnal study: study creation workflow is working properly › Create a new study Error: locator.click: Test timeout of 60000ms exceeded. Call log: - waiting for getByTestId('add-study-button') - locator resolved to <div tabindex="0" role="button" class="study-card emp…>…</div> - attempting click action - waiting for element to be visible, enabled and stable - element was detached from the DOM, retrying at pages/study-page-model.ts:118 116 | 117 | async openStudyCreationModal() { > 118 | await this.getAddStudyBtn.click(); | ^ 119 | } 120 | 121 | async setStudyName(name: string) { at StudyPage.openStudyCreationModal (/app/tests/pages/study-page-model.ts:118:31) at /app/tests/003-study-management.spec.ts:35:21
[webkit] › 003-study-management.spec.ts:29:7 › Test if operationnal study: study creation workflow is working properly › Create a new study: tests/003-study-management.spec.ts#L1
2) [webkit] › 003-study-management.spec.ts:29:7 › Test if operationnal study: study creation workflow is working properly › Create a new study Test timeout of 60000ms exceeded.
[webkit] › 003-study-management.spec.ts:29:7 › Test if operationnal study: study creation workflow is working properly › Create a new study: tests/pages/study-page-model.ts#L118
2) [webkit] › 003-study-management.spec.ts:29:7 › Test if operationnal study: study creation workflow is working properly › Create a new study Error: locator.click: Test timeout of 60000ms exceeded. Call log: - waiting for getByTestId('add-study-button') at pages/study-page-model.ts:118 116 | 117 | async openStudyCreationModal() { > 118 | await this.getAddStudyBtn.click(); | ^ 119 | } 120 | 121 | async setStudyName(name: string) { at StudyPage.openStudyCreationModal (/app/tests/pages/study-page-model.ts:118:31) at /app/tests/003-study-management.spec.ts:35:21
[webkit] › 007-op-rollingstock-tab.spec.ts:92:7 › Verifying that all elements in the rolling stock tab are loaded correctly › should correctly modify a rolling stock for operational study: tests/007-op-rollingstock-tab.spec.ts#L116
3) [webkit] › 007-op-rollingstock-tab.spec.ts:92:7 › Verifying that all elements in the rolling stock tab are loaded correctly › should correctly modify a rolling stock for operational study Error: locator.innerText: Error: strict mode violation: getByTestId('selected-rolling-stock-info') resolved to 2 elements: 1) <span class="rollingstock-info-end" data-testid="selec…>rollingstock_1500_25000_test_e2e</span> aka getByTestId('rollingstock-rollingstock_1500_25000_test_e2e').locator('div').filter({ hasText: 'rollingstock_1500_25000_test_e2eID26' }).first() 2) <span class="rollingstock-info-end" data-testid="selec…>rollingstock_1500_25000_test_e2e</span> aka getByTestId('rollingstock-selector') Call log: - waiting for getByTestId('selected-rolling-stock-info') 114 | await fastRollingstockCard.click(); 115 | await fastRollingstockCard.locator('button').click(); > 116 | expect(await rollingStockSelector.getSelectedRollingStockName.innerText()).toEqual( | ^ 117 | electricRollingStockName 118 | ); 119 | at /app/tests/007-op-rollingstock-tab.spec.ts:116:67
[webkit] › 010-op-route-tab.spec.ts:49:7 › Verifying that all elements in the route tab are loaded correctly › should correctly select a route for operational study: tests/pages/operational-studies-page-model.ts#L372
4) [webkit] › 010-op-route-tab.spec.ts:49:7 › Verifying that all elements in the route tab are loaded correctly › should correctly select a route for operational study Error: locator.innerText: Error: strict mode violation: getByTestId('selected-rolling-stock-info') resolved to 2 elements: 1) <span class="rollingstock-info-end" data-testid="selec…>rollingstock_1500_25000_test_e2e</span> aka getByTestId('rollingstock-rollingstock_1500_25000_test_e2e').locator('div').filter({ hasText: 'rollingstock_1500_25000_test_e2eID26' }).first() 2) <span class="rollingstock-info-end" data-testid="selec…>rollingstock_1500_25000_test_e2e</span> aka getByTestId('rollingstock-selector') Call log: - waiting for getByTestId('selected-rolling-stock-info') at pages/operational-studies-page-model.ts:372 370 | await electricRollingstockCard.click(); 371 | await electricRollingstockCard.locator('button').click(); > 372 | expect(await rollingStockSelector.getSelectedRollingStockName.innerText()).toEqual( | ^ 373 | rollingStockName 374 | ); 375 | } at OperationalStudiesPage.selectRollingStock (/app/tests/pages/operational-studies-page-model.ts:372:67) at /app/tests/010-op-route-tab.spec.ts:63:5
[webkit] › 010-op-route-tab.spec.ts:125:7 › Verifying that all elements in the route tab are loaded correctly › should correctly reverse and delete waypoints in a route for operational study: tests/pages/operational-studies-page-model.ts#L372
5) [webkit] › 010-op-route-tab.spec.ts:125:7 › Verifying that all elements in the route tab are loaded correctly › should correctly reverse and delete waypoints in a route for operational study Error: locator.innerText: Error: strict mode violation: getByTestId('selected-rolling-stock-info') resolved to 2 elements: 1) <span class="rollingstock-info-end" data-testid="selec…>rollingstock_1500_25000_test_e2e</span> aka getByTestId('rollingstock-rollingstock_1500_25000_test_e2e').locator('div').filter({ hasText: 'rollingstock_1500_25000_test_e2eID26' }).first() 2) <span class="rollingstock-info-end" data-testid="selec…>rollingstock_1500_25000_test_e2e</span> aka getByTestId('rollingstock-selector') Call log: - waiting for getByTestId('selected-rolling-stock-info') at pages/operational-studies-page-model.ts:372 370 | await electricRollingstockCard.click(); 371 | await electricRollingstockCard.locator('button').click(); > 372 | expect(await rollingStockSelector.getSelectedRollingStockName.innerText()).toEqual( | ^ 373 | rollingStockName 374 | ); 375 | } at OperationalStudiesPage.selectRollingStock (/app/tests/pages/operational-studies-page-model.ts:372:67) at /app/tests/010-op-route-tab.spec.ts:137:5
check_railjson_generator
The following actions use a deprecated Node.js version and will be forced to run on node20: codecov/codecov-action@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
build (editoast, editoast-test)
The following actions use a deprecated Node.js version and will be forced to run on node20: docker/login-action@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
build (core-build, core)
The following actions use a deprecated Node.js version and will be forced to run on node20: docker/login-action@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
build (gateway-test, gateway-standalone, gateway-front)
The following actions use a deprecated Node.js version and will be forced to run on node20: docker/login-action@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
build (osrdyne, osrdyne-test)
The following actions use a deprecated Node.js version and will be forced to run on node20: docker/login-action@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
build (front-build, front-tests, front-devel, front-nginx)
The following actions use a deprecated Node.js version and will be forced to run on node20: docker/login-action@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
check_core
The following actions use a deprecated Node.js version and will be forced to run on node20: codecov/codecov-action@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
check_editoast_tests
The following actions use a deprecated Node.js version and will be forced to run on node20: codecov/codecov-action@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
check_osrdyne
The following actions use a deprecated Node.js version and will be forced to run on node20: codecov/codecov-action@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
check_gateway
The following actions use a deprecated Node.js version and will be forced to run on node20: codecov/codecov-action@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
check_front
The following actions use a deprecated Node.js version and will be forced to run on node20: codecov/codecov-action@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
integration_tests
The following actions use a deprecated Node.js version and will be forced to run on node20: codecov/codecov-action@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: [webkit] › 008-train-schedule.spec.ts#L1
[webkit] › 008-train-schedule.spec.ts took 25.1s
Slow Test: [chromium] › 006-stdcm-page.spec.ts#L1
[chromium] › 006-stdcm-page.spec.ts took 20.1s
Slow Test: [firefox] › 008-train-schedule.spec.ts#L1
[firefox] › 008-train-schedule.spec.ts took 19.6s
🎭 Playwright Run Summary
5 flaky [firefox] › 003-study-management.spec.ts:29:7 › Test if operationnal study: study creation workflow is working properly › Create a new study [webkit] › 003-study-management.spec.ts:29:7 › Test if operationnal study: study creation workflow is working properly › Create a new study [webkit] › 007-op-rollingstock-tab.spec.ts:92:7 › Verifying that all elements in the rolling stock tab are loaded correctly › should correctly modify a rolling stock for operational study [webkit] › 010-op-route-tab.spec.ts:49:7 › Verifying that all elements in the route tab are loaded correctly › should correctly select a route for operational study [webkit] › 010-op-route-tab.spec.ts:125:7 › Verifying that all elements in the route tab are loaded correctly › should correctly reverse and delete waypoints in a route for operational study 81 passed (5.3m)

Artifacts

Produced during runtime
Name Size
integration-container-logs Expired
175 KB
integration-videos Expired
20.2 MB