core: bump com.rabbitmq:amqp-client from 5.21.0 to 5.22.0 in /core #11020
build.yml
on: pull_request
Matrix: build
check_generated_railjson_sync
25s
check_railjson_generator
1m 49s
check_commits
6s
Check final newline
8s
check_integration_tests
1m 19s
check_osrd_schema
41s
check_toml
4s
check_infra_schema_sync
15s
check_reuse_compliance
8s
check_front_rtk_sync
1m 40s
check_core
3m 59s
check_editoast_tests
4m 11s
check_editoast_lints
5m 0s
check_editoast_openapi
1m 14s
check_gateway
2m 9s
check_osrdyne
2m 40s
check_front
2m 34s
integration_tests
8m 45s
Annotations
5 errors, 15 warnings, and 1 notice
[chromium] › 004-scenario-management.spec.ts:21:7 › Test if operationnal study : scenario creation workflow is working properly › Create a new scenario:
tests/utils/scenario.ts#L27
1) [chromium] › 004-scenario-management.spec.ts:21:7 › Test if operationnal study : scenario creation workflow is working properly › Create a new scenario
TypeError: Cannot read properties of undefined (reading 'id')
at utils/scenario.ts:27
25 | // Create a new scenario with a unique name
26 | const scenario = await postApiRequest(
> 27 | `/api/projects/${project.id}/studies/${study.id}/scenarios/`,
| ^
28 | {
29 | ...scenarioData,
30 | name: `${scenarioData.name} ${uuidv4()}`,
at setupScenario (/app/tests/utils/scenario.ts:27:50)
at /app/tests/004-scenario-management.spec.ts:17:35
|
[firefox] › 004-scenario-management.spec.ts:21:7 › Test if operationnal study : scenario creation workflow is working properly › Create a new scenario:
tests/utils/scenario.ts#L27
2) [firefox] › 004-scenario-management.spec.ts:21:7 › Test if operationnal study : scenario creation workflow is working properly › Create a new scenario
TypeError: Cannot read properties of undefined (reading 'id')
at utils/scenario.ts:27
25 | // Create a new scenario with a unique name
26 | const scenario = await postApiRequest(
> 27 | `/api/projects/${project.id}/studies/${study.id}/scenarios/`,
| ^
28 | {
29 | ...scenarioData,
30 | name: `${scenarioData.name} ${uuidv4()}`,
at setupScenario (/app/tests/utils/scenario.ts:27:50)
at /app/tests/004-scenario-management.spec.ts:17:35
|
[firefox] › 010-op-route-tab.spec.ts:111: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/010-op-route-tab.spec.ts#L1
3) [firefox] › 010-op-route-tab.spec.ts:111:7 › Verifying that all elements in the route tab are loaded correctly › should correctly reverse and delete waypoints in a route for operational study
Test timeout of 90000ms exceeded.
|
[firefox] › 010-op-route-tab.spec.ts:111: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#L255
3) [firefox] › 010-op-route-tab.spec.ts:111: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.waitFor: Test timeout of 90000ms exceeded.
Call log:
- waiting for getByTestId('missing-params-info') to be visible
at pages/operational-studies-page-model.ts:255
253 | ''
254 | );
> 255 | await this.missingParamMessage.waitFor();
| ^
256 | const actualMessage = await this.missingParamMessage.innerText();
257 | expect(actualMessage).toContain(expectedMessage);
258 | }
at OperationalStudiesPage.clickOnDeleteOPButtons (/app/tests/pages/operational-studies-page-model.ts:255:36)
at /app/tests/010-op-route-tab.spec.ts:141:5
|
[webkit] › 006-stdcm-page.spec.ts:18:7 › STDCM page › should configure and launch a stdcm:
tests/pages/simulation-conf-page.ts#L55
4) [webkit] › 006-stdcm-page.spec.ts:18:7 › STDCM page › should configure and launch a stdcm ─────
Error: expect(locator).toBeVisible()
Locator: getByTestId('typeandpath-op-NES')
Expected: visible
Received: hidden
Call log:
- expect.toBeVisible with timeout 10000ms
- waiting for getByTestId('typeandpath-op-NES')
at pages/simulation-conf-page.ts:55
53 | this.page.getByTestId(`typeandpath-op-${firstTrigram}`) &&
54 | this.page.getByTestId(`typeandpath-op-${secondTrigram}`)
> 55 | ).toBeVisible();
| ^
56 | await this.searchByTrigramSubmitButton.click();
57 | await expect(this.pathfindingDoneLabel).toBeVisible();
58 | }
at StdcmPage.selectPathByTrigram (/app/tests/pages/simulation-conf-page.ts:55:7)
at /app/tests/006-stdcm-page.spec.ts:47:5
|
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 (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 (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/
|
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/
|
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 (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/
|
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/
|
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_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/
|
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:
[chromium] › 009-rollingstock-editor.spec.ts#L1
[chromium] › 009-rollingstock-editor.spec.ts took 36.6s
|
Slow Test:
[webkit] › 008-train-schedule.spec.ts#L1
[webkit] › 008-train-schedule.spec.ts took 30.5s
|
Slow Test:
[chromium] › 006-stdcm-page.spec.ts#L1
[chromium] › 006-stdcm-page.spec.ts took 16.3s
|
🎭 Playwright Run Summary
4 flaky
[chromium] › 004-scenario-management.spec.ts:21:7 › Test if operationnal study : scenario creation workflow is working properly › Create a new scenario
[firefox] › 004-scenario-management.spec.ts:21:7 › Test if operationnal study : scenario creation workflow is working properly › Create a new scenario
[firefox] › 010-op-route-tab.spec.ts:111:7 › Verifying that all elements in the route tab are loaded correctly › should correctly reverse and delete waypoints in a route for operational study
[webkit] › 006-stdcm-page.spec.ts:18:7 › STDCM page › should configure and launch a stdcm ──────
82 passed (5.3m)
|
Artifacts
Produced during runtime
Name | Size | |
---|---|---|
integration-container-logs
|
233 KB |
|
integration-videos
|
20.4 MB |
|