Skip to content
build-core

Adding Allocation and Partition - New Approach #246

Sign in to view logs

Adding Allocation and Partition - New Approach

Adding Allocation and Partition - New Approach #246

Triggered via pull request September 13, 2024 17:53
@JTSIV1JTSIV1
synchronize #117
JTSIV1:allocation_partition_app2
Status Failure
Total duration 36s
Artifacts –

build-core.yml

on: pull_request
build
24s
build
lint
26s
lint
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 4 warnings
build: src/connectors/SlurmConnector.ts#L38
Object is possibly 'null'.
build
Process completed with exit code 2.
build
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions/setup-node@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
lint
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
lint
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions/setup-node@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/