core: add the posibility to use hostname as WORKEY_ID #12748
build.yml
on: push
Matrix: build
check_generated_railjson_sync
25s
check_railjson_generator
1m 57s
check_commits
6s
Check final newline
13s
check_integration_tests
1m 27s
check_osrd_schema
39s
check_toml
5s
check_infra_schema_sync
18s
check_reuse_compliance
10s
check_front_rtk_sync
1m 28s
check_core
3m 59s
check_editoast_tests
6m 22s
check_editoast_lints
8m 44s
check_editoast_openapi
1m 3s
check_gateway
3m 19s
check_osrdyne
3m 12s
check_front
2m 24s
integration_tests
9m 34s
Annotations
7 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
|
[firefox] › 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/011-op-times-and-stops-tab.spec.ts#L1
3) [firefox] › 011-op-times-and-stops-tab.spec.ts:75:7 › Times and Stops Tab Verification › should correctly set and display times and stops tables
Test timeout of 90000ms exceeded.
|
[firefox] › 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/op-timetable-page-model.ts#L198
3) [firefox] › 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.scrollIntoViewIfNeeded: Test timeout of 90000ms exceeded.
Call log:
- waiting for locator('.time-stops-datasheet')
at pages/op-timetable-page-model.ts:198
196 |
197 | async verifyTimeStopsDatasheetVisibility(timeout = 30 * 1000): Promise<void> {
> 198 | await this.timeStopsDatasheet.scrollIntoViewIfNeeded();
| ^
199 | // Wait for the Times and Stops simulation datasheet to be fully loaded with a specified timeout (default: 30 seconds)
200 | await expect(this.timeStopsDatasheet).toBeVisible({ timeout });
201 | }
at OperationalStudiesTimetablePage.verifyTimeStopsDatasheetVisibility (/app/tests/pages/op-timetable-page-model.ts:198:35)
at /app/tests/011-op-times-and-stops-tab.spec.ts:160:21
|
[firefox] › 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/op-output-table-page-model.ts#L31
3) [firefox] › 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.waitFor: Test timeout of 90000ms exceeded.
Call log:
- waiting for locator('[class="dsg-cell dsg-cell-header"] .dsg-cell-header-container').first() to be visible
at pages/op-output-table-page-model.ts:31
29 | // Extract the column index for each header name
30 | async getHeaderIndexMap(): Promise<Record<string, number>> {
> 31 | await this.columnHeaders.first().waitFor({ state: 'visible' });
| ^
32 | const headers = await this.columnHeaders.allTextContents();
33 | const headerMap: Record<string, number> = {};
34 | headers.forEach((header, index) => {
at OperationalStudiesOutputTablePage.getHeaderIndexMap (/app/tests/pages/op-output-table-page-model.ts:31:38)
at OperationalStudiesOutputTablePage.getOutputTableData (/app/tests/pages/op-output-table-page-model.ts:44:39)
at /app/tests/011-op-times-and-stops-tab.spec.ts:163:29
|
[webkit] › 010-op-route-tab.spec.ts:67:7 › Verifying that all elements in the route tab are loaded correctly › should correctly add waypoints in a route for operational study:
tests/pages/operational-studies-page-model.ts#L400
4) [webkit] › 010-op-route-tab.spec.ts:67:7 › Verifying that all elements in the route tab are loaded correctly › should correctly add 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_e2eID30' }).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: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:78:5
|
[webkit] › 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#L400
5) [webkit] › 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.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_e2eID30' }).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: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:123:5
|
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 (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 (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 (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_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:
[webkit] › 008-train-schedule.spec.ts#L1
[webkit] › 008-train-schedule.spec.ts took 27.0s
|
🎭 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
[firefox] › 011-op-times-and-stops-tab.spec.ts:75:7 › Times and Stops Tab Verification › should correctly set and display times and stops tables
[webkit] › 010-op-route-tab.spec.ts:67:7 › Verifying that all elements in the route tab are loaded correctly › should correctly add waypoints in a route for operational study
[webkit] › 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
3 skipped
84 passed (5.9m)
|
Artifacts
Produced during runtime
Name | Size | |
---|---|---|
integration-container-logs
|
244 KB |
|
integration-videos
|
23.7 MB |
|