Skip to content

front: add times and stops e2e test for operational studies #11974

front: add times and stops e2e test for operational studies

front: add times and stops e2e test for operational studies #11974

Re-run triggered October 1, 2024 14:03
Status Success
Total duration 11m 26s
Artifacts 2

build.yml

on: pull_request
Matrix: build
check_generated_railjson_sync
21s
check_generated_railjson_sync
check_railjson_generator
1m 56s
check_railjson_generator
check_commits
10s
check_commits
Check final newline
7s
Check final newline
check_integration_tests
1m 23s
check_integration_tests
check_osrd_schema
40s
check_osrd_schema
check_toml
6s
check_toml
check_infra_schema_sync
20s
check_infra_schema_sync
check_reuse_compliance
9s
check_reuse_compliance
Fit to window
Zoom out
Zoom in

Annotations

4 errors, 13 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
[webkit] › 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
3) [webkit] › 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
[webkit] › 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
3) [webkit] › 004-scenario-management.spec.ts:21:7 › Test if operationnal study : scenario creation workflow is working properly › Create a new scenario Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── 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
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 (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/
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/
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/
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_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_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_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 35.3s
🎭 Playwright Run Summary
3 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 [webkit] › 004-scenario-management.spec.ts:21:7 › Test if operationnal study : scenario creation workflow is working properly › Create a new scenario 3 skipped 86 passed (5.4m)

Artifacts

Produced during runtime
Name Size
integration-container-logs Expired
247 KB
integration-videos Expired
4.76 MB