Skip to content

editoast: bump proc-macro2 from 1.0.86 to 1.0.87 in /editoast #12444

editoast: bump proc-macro2 from 1.0.86 to 1.0.87 in /editoast

editoast: bump proc-macro2 from 1.0.86 to 1.0.87 in /editoast #12444

Triggered via pull request October 7, 2024 19:03
Status Success
Total duration 29m 55s
Artifacts 2

build.yml

on: pull_request
Matrix: build
check_generated_railjson_sync
25s
check_generated_railjson_sync
check_railjson_generator
1m 57s
check_railjson_generator
check_commits
10s
check_commits
Check final newline
9s
Check final newline
check_integration_tests
1m 26s
check_integration_tests
check_osrd_schema
37s
check_osrd_schema
check_toml
9s
check_toml
check_infra_schema_sync
16s
check_infra_schema_sync
check_reuse_compliance
14s
check_reuse_compliance
Fit to window
Zoom out
Zoom in

Annotations

6 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
[webkit] › 010-op-route-tab.spec.ts:35: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#L400
4) [webkit] › 010-op-route-tab.spec.ts:35: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 3 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_e2eID30' }).first() 2) <span class="rollingstock-info-end" data-testid="selec…>rollingstock_1500_25000_test_e2e-467</span> aka getByTestId('rollingstock-rollingstock_1500_25000_test_e2e-467').locator('div').filter({ hasText: 'rollingstock_1500_25000_test_e2e-467ID39' }).first() 3) <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:400 398 | await electricRollingstockCard.click(); 399 | await electricRollingstockCard.locator('button').click(); > 400 | expect(await rollingStockSelector.getSelectedRollingStockName.innerText()).toEqual( | ^ 401 | rollingStockName 402 | ); 403 | } at OperationalStudiesPage.selectRollingStock (/app/tests/pages/operational-studies-page-model.ts:400:67) at /app/tests/010-op-route-tab.spec.ts:49:5
[webkit] › 011-op-times-and-stops-tab.spec.ts:75:7 › Times and Stops Tab Verification › should correctly set and display times and stops tables: tests/pages/operational-studies-page-model.ts#L400
5) [webkit] › 011-op-times-and-stops-tab.spec.ts:75:7 › Times and Stops Tab Verification › should correctly set and display times and stops tables 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…>dual-mode_rollingstock_test_e2e</span> aka getByTestId('rollingstock-dual-mode_rollingstock_test_e2e').locator('div').filter({ hasText: 'dual-modedual-modedual-' }).first() 2) <span class="rollingstock-info-end" data-testid="selec…>dual-mode_rollingstock_test_e2e</span> aka getByTestId('rollingstock-selector') Call log: - waiting for getByTestId('selected-rolling-stock-info') at pages/operational-studies-page-model.ts:400 398 | await electricRollingstockCard.click(); 399 | await electricRollingstockCard.locator('button').click(); > 400 | expect(await rollingStockSelector.getSelectedRollingStockName.innerText()).toEqual( | ^ 401 | rollingStockName 402 | ); 403 | } at OperationalStudiesPage.selectRollingStock (/app/tests/pages/operational-studies-page-model.ts:400:67) at /app/tests/011-op-times-and-stops-tab.spec.ts:97: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 (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/
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/
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_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_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] › 005-operational-studies.spec.ts#L1
[chromium] › 005-operational-studies.spec.ts took 17.1s
🎭 Playwright Run Summary
5 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 [webkit] › 010-op-route-tab.spec.ts:35:7 › Verifying that all elements in the route tab are loaded correctly › should correctly select a route for operational study [webkit] › 011-op-times-and-stops-tab.spec.ts:75:7 › Times and Stops Tab Verification › should correctly set and display times and stops tables 3 skipped 84 passed (5.5m)

Artifacts

Produced during runtime
Name Size
integration-container-logs Expired
246 KB
integration-videos Expired
20.6 MB