front: bump @playwright/test from 1.43.1 to 1.50.0 in /front #18289
dependabot[bot]build.yml
on: pull_request
Matrix: Build
Check dockerfiles
14s
Check scripts
4s
Check generated railjson sync
27s
Check railjson generator
1m 55s
Check commits
10s
Check final newline
16s
Check integration tests
1m 23s
Check osrd schema
47s
Check toml
5s
Check infra schema sync
24s
Check reuse compliance
12s
Check front rtk sync
1m 15s
Check core
4m 13s
Check editoast tests
7m 14s
Check editoast lints
8m 46s
Check editoast openapi
43s
Check gateway
3m 26s
Check osrdyne
3m 42s
Check front
3m 14s
Integration tests
1m 19s
End to end tests
19m 3s
Annotations
10 errors, 28 warnings, and 1 notice
|
[chromium] › tests/002-project-management.spec.ts:15:7 › Validate the Operational Study Project workflow › Create a new project:
tests/utils/api-setup.ts#L103
1) [chromium] › tests/002-project-management.spec.ts:15:7 › Validate the Operational Study Project workflow › Create a new project
Error: apiRequestContext.delete: Parse Error: Expected HTTP/
Call log:
- → DELETE http://localhost:4000/api/projects/3
- user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/133.0.6943.16 Safari/537.36
- accept: */*
- accept-encoding: gzip,deflate,br
- ← 204 No Content
- vary: origin, access-control-request-method, access-control-request-headers, Origin, Access-Control-Request-Method, Access-Control-Request-Headers
- access-control-allow-origin: *
- date: Mon, 27 Jan 2025 18:41:06 GMT
at utils/api-setup.ts:103
101 | ): Promise<APIResponse> => {
102 | const apiContext = await getApiContext();
> 103 | const response = await apiContext.delete(url);
| ^
104 | handleErrorResponse(response, errorMessage);
105 | return response;
106 | };
at deleteApiRequest (/app/front/tests/utils/api-setup.ts:103:43)
at deleteProject (/app/front/tests/utils/teardown-utils.ts:41:5)
at /app/front/tests/002-project-management.spec.ts:45:5
|
|
[chromium] › tests/002-project-management.spec.ts:15:7 › Validate the Operational Study Project workflow › Create a new project:
tests/utils/api-setup.ts#L103
1) [chromium] › tests/002-project-management.spec.ts:15:7 › Validate the Operational Study Project workflow › Create a new project
Retry #1 ───────────────────────────────────────────────────────────────────────────────────────
Error: apiRequestContext.delete: Parse Error: Expected HTTP/
Call log:
- → DELETE http://localhost:4000/api/projects/5
- user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/133.0.6943.16 Safari/537.36
- accept: */*
- accept-encoding: gzip,deflate,br
- ← 204 No Content
- access-control-allow-origin: *
- date: Mon, 27 Jan 2025 18:41:09 GMT
- vary: origin, access-control-request-method, access-control-request-headers, Origin, Access-Control-Request-Method, Access-Control-Request-Headers
at utils/api-setup.ts:103
101 | ): Promise<APIResponse> => {
102 | const apiContext = await getApiContext();
> 103 | const response = await apiContext.delete(url);
| ^
104 | handleErrorResponse(response, errorMessage);
105 | return response;
106 | };
at deleteApiRequest (/app/front/tests/utils/api-setup.ts:103:43)
at deleteProject (/app/front/tests/utils/teardown-utils.ts:41:5)
at /app/front/tests/002-project-management.spec.ts:45:5
|
|
[chromium] › tests/002-project-management.spec.ts:15:7 › Validate the Operational Study Project workflow › Create a new project:
tests/utils/api-setup.ts#L103
1) [chromium] › tests/002-project-management.spec.ts:15:7 › Validate the Operational Study Project workflow › Create a new project
Retry #2 ───────────────────────────────────────────────────────────────────────────────────────
Error: apiRequestContext.delete: Parse Error: Expected HTTP/
Call log:
- → DELETE http://localhost:4000/api/projects/7
- user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/133.0.6943.16 Safari/537.36
- accept: */*
- accept-encoding: gzip,deflate,br
- ← 204 No Content
- vary: origin, access-control-request-method, access-control-request-headers, Origin, Access-Control-Request-Method, Access-Control-Request-Headers
- access-control-allow-origin: *
- date: Mon, 27 Jan 2025 18:41:12 GMT
at utils/api-setup.ts:103
101 | ): Promise<APIResponse> => {
102 | const apiContext = await getApiContext();
> 103 | const response = await apiContext.delete(url);
| ^
104 | handleErrorResponse(response, errorMessage);
105 | return response;
106 | };
at deleteApiRequest (/app/front/tests/utils/api-setup.ts:103:43)
at deleteProject (/app/front/tests/utils/teardown-utils.ts:41:5)
at /app/front/tests/002-project-management.spec.ts:45:5
|
|
[chromium] › tests/002-project-management.spec.ts:49:7 › Validate the Operational Study Project workflow › Update an existing project:
tests/utils/api-setup.ts#L103
2) [chromium] › tests/002-project-management.spec.ts:49:7 › Validate the Operational Study Project workflow › Update an existing project
Error: apiRequestContext.delete: Parse Error: Expected HTTP/
Call log:
- → DELETE http://localhost:4000/api/projects/4
- user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/133.0.6943.16 Safari/537.36
- accept: */*
- accept-encoding: gzip,deflate,br
- ← 204 No Content
- date: Mon, 27 Jan 2025 18:41:09 GMT
- vary: origin, access-control-request-method, access-control-request-headers, Origin, Access-Control-Request-Method, Access-Control-Request-Headers
- access-control-allow-origin: *
at utils/api-setup.ts:103
101 | ): Promise<APIResponse> => {
102 | const apiContext = await getApiContext();
> 103 | const response = await apiContext.delete(url);
| ^
104 | handleErrorResponse(response, errorMessage);
105 | return response;
106 | };
at deleteApiRequest (/app/front/tests/utils/api-setup.ts:103:43)
at deleteProject (/app/front/tests/utils/teardown-utils.ts:41:5)
at /app/front/tests/002-project-management.spec.ts:86:5
|
|
[chromium] › tests/002-project-management.spec.ts:49:7 › Validate the Operational Study Project workflow › Update an existing project:
tests/utils/api-setup.ts#L103
2) [chromium] › tests/002-project-management.spec.ts:49:7 › Validate the Operational Study Project workflow › Update an existing project
Retry #1 ───────────────────────────────────────────────────────────────────────────────────────
Error: apiRequestContext.delete: Parse Error: Expected HTTP/
Call log:
- → DELETE http://localhost:4000/api/projects/6
- user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/133.0.6943.16 Safari/537.36
- accept: */*
- accept-encoding: gzip,deflate,br
- ← 204 No Content
- access-control-allow-origin: *
- date: Mon, 27 Jan 2025 18:41:13 GMT
- vary: origin, access-control-request-method, access-control-request-headers, Origin, Access-Control-Request-Method, Access-Control-Request-Headers
at utils/api-setup.ts:103
101 | ): Promise<APIResponse> => {
102 | const apiContext = await getApiContext();
> 103 | const response = await apiContext.delete(url);
| ^
104 | handleErrorResponse(response, errorMessage);
105 | return response;
106 | };
at deleteApiRequest (/app/front/tests/utils/api-setup.ts:103:43)
at deleteProject (/app/front/tests/utils/teardown-utils.ts:41:5)
at /app/front/tests/002-project-management.spec.ts:86:5
|
|
[chromium] › tests/002-project-management.spec.ts:49:7 › Validate the Operational Study Project workflow › Update an existing project:
tests/utils/api-setup.ts#L103
2) [chromium] › tests/002-project-management.spec.ts:49:7 › Validate the Operational Study Project workflow › Update an existing project
Retry #2 ───────────────────────────────────────────────────────────────────────────────────────
Error: apiRequestContext.delete: Parse Error: Expected HTTP/
Call log:
- → DELETE http://localhost:4000/api/projects/9
- user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/133.0.6943.16 Safari/537.36
- accept: */*
- accept-encoding: gzip,deflate,br
- ← 204 No Content
- vary: origin, access-control-request-method, access-control-request-headers, Origin, Access-Control-Request-Method, Access-Control-Request-Headers
- access-control-allow-origin: *
- date: Mon, 27 Jan 2025 18:41:17 GMT
at utils/api-setup.ts:103
101 | ): Promise<APIResponse> => {
102 | const apiContext = await getApiContext();
> 103 | const response = await apiContext.delete(url);
| ^
104 | handleErrorResponse(response, errorMessage);
105 | return response;
106 | };
at deleteApiRequest (/app/front/tests/utils/api-setup.ts:103:43)
at deleteProject (/app/front/tests/utils/teardown-utils.ts:41:5)
at /app/front/tests/002-project-management.spec.ts:86:5
|
|
[chromium] › tests/003-study-management.spec.ts:31:7 › Validate the Study creation workflow › Create a new study:
tests/utils/api-setup.ts#L103
3) [chromium] › tests/003-study-management.spec.ts:31:7 › Validate the Study creation workflow › Create a new study
Error: apiRequestContext.delete: Parse Error: Expected HTTP/
Call log:
- → DELETE http://localhost:4000/api/projects/1/studies/3
- user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/133.0.6943.16 Safari/537.36
- accept: */*
- accept-encoding: gzip,deflate,br
- ← 204 No Content
- date: Mon, 27 Jan 2025 18:41:18 GMT
- vary: origin, access-control-request-method, access-control-request-headers, Origin, Access-Control-Request-Method, Access-Control-Request-Headers
- access-control-allow-origin: *
at utils/api-setup.ts:103
101 | ): Promise<APIResponse> => {
102 | const apiContext = await getApiContext();
> 103 | const response = await apiContext.delete(url);
| ^
104 | handleErrorResponse(response, errorMessage);
105 | return response;
106 | };
at deleteApiRequest (/app/front/tests/utils/api-setup.ts:103:43)
at deleteStudy (/app/front/tests/utils/teardown-utils.ts:84:5)
at /app/front/tests/003-study-management.spec.ts:70:5
|
|
[chromium] › tests/003-study-management.spec.ts:31:7 › Validate the Study creation workflow › Create a new study:
tests/utils/api-setup.ts#L103
3) [chromium] › tests/003-study-management.spec.ts:31:7 › Validate the Study creation workflow › Create a new study
Retry #1 ───────────────────────────────────────────────────────────────────────────────────────
Error: apiRequestContext.delete: Parse Error: Expected HTTP/
Call log:
- → DELETE http://localhost:4000/api/projects/1/studies/5
- user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/133.0.6943.16 Safari/537.36
- accept: */*
- accept-encoding: gzip,deflate,br
- ← 204 No Content
- vary: origin, access-control-request-method, access-control-request-headers, Origin, Access-Control-Request-Method, Access-Control-Request-Headers
- access-control-allow-origin: *
- date: Mon, 27 Jan 2025 18:41:23 GMT
at utils/api-setup.ts:103
101 | ): Promise<APIResponse> => {
102 | const apiContext = await getApiContext();
> 103 | const response = await apiContext.delete(url);
| ^
104 | handleErrorResponse(response, errorMessage);
105 | return response;
106 | };
at deleteApiRequest (/app/front/tests/utils/api-setup.ts:103:43)
at deleteStudy (/app/front/tests/utils/teardown-utils.ts:84:5)
at /app/front/tests/003-study-management.spec.ts:70:5
|
|
[chromium] › tests/003-study-management.spec.ts:31:7 › Validate the Study creation workflow › Create a new study:
tests/utils/api-setup.ts#L103
3) [chromium] › tests/003-study-management.spec.ts:31:7 › Validate the Study creation workflow › Create a new study
Retry #2 ───────────────────────────────────────────────────────────────────────────────────────
Error: apiRequestContext.delete: Parse Error: Expected HTTP/
Call log:
- → DELETE http://localhost:4000/api/projects/1/studies/6
- user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/133.0.6943.16 Safari/537.36
- accept: */*
- accept-encoding: gzip,deflate,br
- ← 204 No Content
- vary: origin, access-control-request-method, access-control-request-headers, Origin, Access-Control-Request-Method, Access-Control-Request-Headers
- access-control-allow-origin: *
- date: Mon, 27 Jan 2025 18:41:33 GMT
at utils/api-setup.ts:103
101 | ): Promise<APIResponse> => {
102 | const apiContext = await getApiContext();
> 103 | const response = await apiContext.delete(url);
| ^
104 | handleErrorResponse(response, errorMessage);
105 | return response;
106 | };
at deleteApiRequest (/app/front/tests/utils/api-setup.ts:103:43)
at deleteStudy (/app/front/tests/utils/teardown-utils.ts:84:5)
at /app/front/tests/003-study-management.spec.ts:70:5
|
|
[chromium] › tests/003-study-management.spec.ts:74:7 › Validate the Study creation workflow › Update an existing study:
tests/utils/api-setup.ts#L103
4) [chromium] › tests/003-study-management.spec.ts:74:7 › Validate the Study creation workflow › Update an existing study
Error: apiRequestContext.delete: Parse Error: Expected HTTP/
Call log:
- → DELETE http://localhost:4000/api/projects/1/studies/7
- user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/133.0.6943.16 Safari/537.36
- accept: */*
- accept-encoding: gzip,deflate,br
- ← 204 No Content
- access-control-allow-origin: *
- date: Mon, 27 Jan 2025 18:41:37 GMT
- vary: origin, access-control-request-method, access-control-request-headers, Origin, Access-Control-Request-Method, Access-Control-Request-Headers
at utils/api-setup.ts:103
101 | ): Promise<APIResponse> => {
102 | const apiContext = await getApiContext();
> 103 | const response = await apiContext.delete(url);
| ^
104 | handleErrorResponse(response, errorMessage);
105 | return response;
106 | };
at deleteApiRequest (/app/front/tests/utils/api-setup.ts:103:43)
at deleteStudy (/app/front/tests/utils/teardown-utils.ts:84:5)
at /app/front/tests/003-study-management.spec.ts:117:5
|
|
Check scripts
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Check toml
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Check commits
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Check dockerfiles
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Check final newline
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Check reuse compliance
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Build (editoast, editoast-test)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Check infra schema sync
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Check generated railjson sync
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Build (osrdyne, osrdyne-test)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Build (core-build, core)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Check osrd schema
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Check integration tests
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Check railjson generator
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Build (gateway-test, gateway-standalone, gateway-front)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Build (front-build, front-tests, front-devel, front-nginx)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Check editoast openapi
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Check front rtk sync
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Integration tests
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Check gateway
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Check core
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Check osrdyne
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Check front
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Check editoast tests
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Check editoast lints
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
End to end tests
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Slow Test:
[chromium] › tests/013-stdcm-simulation-sheet.spec.ts#L1
[chromium] › tests/013-stdcm-simulation-sheet.spec.ts took 31.1s
|
|
Slow Test:
[firefox] › tests/013-stdcm-simulation-sheet.spec.ts#L1
[firefox] › tests/013-stdcm-simulation-sheet.spec.ts took 25.5s
|
|
🎭 Playwright Run Summary
40 failed
[chromium] › tests/002-project-management.spec.ts:15:7 › Validate the Operational Study Project workflow › Create a new project
[chromium] › tests/002-project-management.spec.ts:49:7 › Validate the Operational Study Project workflow › Update an existing project
[chromium] › tests/003-study-management.spec.ts:31:7 › Validate the Study creation workflow › Create a new study
[chromium] › tests/003-study-management.spec.ts:74:7 › Validate the Study creation workflow › Update an existing study
[chromium] › tests/004-scenario-management.spec.ts:31:7 › Validate the Scenario creation workflow › Create a new scenario
[chromium] › tests/004-scenario-management.spec.ts:58:7 › Validate the Scenario creation workflow › Update an existing scenario
[chromium] › tests/004-scenario-management.spec.ts:97:7 › Validate the Scenario creation workflow › Delete a scenario
[chromium] › tests/005-operational-studies.spec.ts:43:7 › Verify simulation configuration in operational studies › Pathfinding with rolling stock and composition code
[chromium] › tests/007-op-rollingstock-tab.spec.ts:47:7 › Rolling stock Tab Verification › Select a rolling stock for operational study
[chromium] › tests/007-op-rollingstock-tab.spec.ts:80:7 › Rolling stock Tab Verification › Modify a rolling stock for operational study
[chromium] › tests/009-rollingstock-editor.spec.ts:42:7 › Rollingstock editor page tests › Create a new rolling stock
[chromium] › tests/009-rollingstock-editor.spec.ts:106:7 › Rollingstock editor page tests › Duplicate and modify a rolling stock
[chromium] › tests/010-op-route-tab.spec.ts:80:7 › Route Tab Verification › Adding waypoints to a route for operational study
[chromium] › tests/010-op-route-tab.spec.ts:110:7 › Route Tab Verification › Reversing and deleting waypoints in a route for operational study
[chromium] › tests/011-op-times-and-stops-tab.spec.ts:115:7 › Times and Stops Tab Verification › should correctly set and display times and stops tables
[chromium] › tests/011-op-times-and-stops-tab.spec.ts:183:7 › Times and Stops Tab Verification › should correctly update and clear input table row
[chromium] › tests/012-op-simulation-settings-tab.spec.ts:134:7 › Simulation Settings Tab Verification › Activate electrical profiles
[chromium] › tests/012-op-simulation-settings-tab.spec.ts:215:7 › Simulation Settings Tab Verification › Activate composition code
[chromium] › tests/012-op-simulation-settings-tab.spec.ts:295:7 › Simulation Settings Tab Verification › Activate linear and mareco margin
[chromium] › tests/012-op-simulation-settings-tab.spec.ts:384:7 › Simulation Settings Tab Verification › Add all the simulation settings
[firefox] › tests/002-project-management.spec.ts:15:7 › Validate the Operational Study Project workflow › Create a new project
[firefox] › tests/002-project-management.spec.ts:49:7 › Validate the Operational Study Project workflow › Update an existing project
[firefox] › tests/003-study-management.spec.ts:31:7 › Validate the Study creation workflow › Create a new study
[firefox] › tests/003-study-management.spec.ts:74:7 › Validate the Study creation workflow › Update an existing study
[firefox] › tests/004-scenario-management.spec.ts:31:7 › Validate the Scenario creation workflow › Create a new scenario
[firefox] › tests/004-scenario-management.spec.ts:58:7 › Validate the Scenario creation workflow › Update an existing scenario
[firefox] › tests/004-scenario-management.spec.ts:97:7 › Validate the Scenario creation workflow › Delete a scenario
[firefox] › tests/005-operational-studies.spec.ts:43:7 › Verify simulation configuration in operational studies › Pathfinding with rolling stock and composition code
[firefox] › tests/007-op-rollingstock-tab.spec.ts:47:7 › Rolling stock Tab Verification › Select a rolling stock for operational study
[firefox] › tests/007-op-rollingstock-tab.spec.ts:80:7 › Rolling stock Tab Verification › Modify a rolling stock for oper
|
Artifacts
Produced during runtime
| Name | Size | |
|---|---|---|
|
e2e-container-logs
|
678 KB |
|
|
integration-container-logs
|
32.8 KB |
|
|
integration-videos
|
286 MB |
|