From 19342da48308ee10acb6896f6a1f2e495bc8d5f0 Mon Sep 17 00:00:00 2001 From: John Reiland <93950341+jreiland@users.noreply.github.com> Date: Thu, 23 Jul 2026 15:45:59 -0600 Subject: [PATCH 1/4] Delete docs/running-jobs/squeue-status-codes.md --- docs/running-jobs/squeue-status-codes.md | 52 ------------------------ 1 file changed, 52 deletions(-) delete mode 100644 docs/running-jobs/squeue-status-codes.md diff --git a/docs/running-jobs/squeue-status-codes.md b/docs/running-jobs/squeue-status-codes.md deleted file mode 100644 index 911bc9984..000000000 --- a/docs/running-jobs/squeue-status-codes.md +++ /dev/null @@ -1,52 +0,0 @@ -# `squeue` Status and Reason Codes - -The `squeue` command details a variety of information on an active -job’s status with state and reason codes. *__Job state -codes__* describe a job’s current state in queue (e.g. pending, -completed). *__Job reason codes__* describe the reason why the job is -in its current state. - -The following tables outline a variety of job state and reason codes you -may encounter when using squeue to check on your jobs. - -## Job State Codes - -| Status | Code | Explaination | -| ------------- | :---: | ---------------------------------------------------------------------- | -| COMPLETED | `CD` | The job has completed successfully. | -| COMPLETING | `CG` | The job is finishing but some processes are still active. | -| FAILED | `F` | The job terminated with a non-zero exit code and failed to execute. | -| PENDING | `PD` | The job is waiting for resource allocation. It will eventually run. | -| PREEMPTED | `PR` | The job was terminated because of preemption by another job. | -| RUNNING | `R` | The job currently is allocated to a node and is running. | -| SUSPENDED | `S` | A running job has been stopped with its cores released to other jobs. | -| STOPPED | `ST` | A running job has been stopped with its cores retained. | - -```{seealso} -A full list of these Job State codes can be found in [Slurm’s -documentation.](https://slurm.schedmd.com/squeue.html#lbAG) -``` - -## Job Reason Codes - -| Reason Code | Explanation | -| ------------------------ | ------------------------------------------------------------------------------------------- | -| `Priority` | One or more higher priority jobs is in queue for running. Your job will eventually run. | -| `Dependency` | This job is waiting for a dependent job to complete and will run afterward. | -| `Resources` | The job is waiting for resources to become available and will eventually run. | -| `InvalidAccount` | The job’s account is invalid. Cancel the job and rerun with the correct account. | -| `InvaldQoS` | The job’s QoS is invalid. Cancel the job and rerun with the correct account. | -| `QOSGrpCpuLimit` | All CPUs assigned to your job’s specified QoS are in use; the job will run eventually. | -| `QOSGrpMaxJobsLimit` | Maximum number of jobs for your job’s QoS have been met; the job will run eventually. | -| `QOSGrpNodeLimit` | All nodes assigned to your job’s specified QoS are in use; the job will run eventually. | -| `PartitionCpuLimit` | All CPUs assigned to your job’s specified partition are in use; the job will run eventually. | -| `PartitionMaxJobsLimit` | Maximum number of jobs for your job’s partition have been met; the job will run eventually. | -| `PartitionNodeLimit` | All nodes assigned to your job’s specified partition are in use; the job will run eventually. | -| `AssociationCpuLimit` | All CPUs assigned to your job’s specified association are in use; the job will run eventually. | -| `AssociationMaxJobsLimit`| Maximum number of jobs for your job’s association have been met; the job will run eventually. | -| `AssociationNodeLimit` | All nodes assigned to your job’s specified association are in use; the job will run eventually. | - -```{seealso} -A full list of these Job Reason Codes can be found [in Slurm’s -documentation.](https://slurm.schedmd.com/squeue.html#lbAF) -``` From babed74c4210514ca17d118c6e47ad2f52b50d60 Mon Sep 17 00:00:00 2001 From: John Reiland <93950341+jreiland@users.noreply.github.com> Date: Thu, 23 Jul 2026 15:50:46 -0600 Subject: [PATCH 2/4] Add new error/status codes page --- docs/running-jobs/error-status-codes.md | 83 +++++++++++++++++++++++++ 1 file changed, 83 insertions(+) create mode 100644 docs/running-jobs/error-status-codes.md diff --git a/docs/running-jobs/error-status-codes.md b/docs/running-jobs/error-status-codes.md new file mode 100644 index 000000000..8ec509ed8 --- /dev/null +++ b/docs/running-jobs/error-status-codes.md @@ -0,0 +1,83 @@ +# Job Submission and Status Error and Reason Codes + +## Alpine Job Submission Error Codes + +| **#** | **Error Message** | **Cause / Explanation** | **Resolution / Action** | +| --- | --- | --- | --- | +| 1 | The `` partition accepts the following QoS values: `` | You have provided a QoS value that is not supported by the requested partition. | Use a supported QoS from the list given in the error output. | +| 2 | Please modify your provided `GRES` so that the `GRES` type is specified. For the `` partition and `` QoS, valid GRES are as follows (where `N` is the number of GPUs): `` | You have not specified a `GRES` type in your provided `--gres` option. | Select a valid `GRES` type from the list provided in the error message. | +| 3 | Users must specify `--nodes` for all GPU partitions. | You have not specified a number of nodes in your job request, which is required on all GPU partitions. | Specify a number of nodes using the `--nodes=N` directive, where N is the number of nodes to request. | +| 4 | All GPU jobs are limited to 1 node. Please reschedule your job using `--nodes=1`. | You have requested more than one node (the maximum allowed) on a GPU partition. | Reschedule your job using `--nodes=1`. | +| 5 | When requesting resources on the `` partition, users must specify `--gres`. | You have not specified a `GRES` using the `--gres` directive, which is required on this partition. | Specify a `GRES` using the `--gres` directive. | +| 6 | A list of `gres` options is currently not permitted. | You have provided a comma-separated list of `GRES` options, which is not permitted. | Specify only one `GRES` option. | +| 7 | An invalid `--gres` input was provided. | You have provided an invalid `--gres` option. | Please check the spelling of your `--gres` input and try again. | +| 8 | For GPU partitions, users must use the `gres` name `gpu`. | You have specified a `gres` option other than `gpu` on a GPU partition. | Please specify `gpu` as the `gres` name. | +| 9 | Since a `GRES` type was not specified, `GRES` has been set to `--gres=`. | You did not specify a `GRES` type, so one was automatically selected. | Please specify a `gres` type (for example, `--gres=gpu:a100-40gb`) in the future. | +| 10 | An invalid `GRES` type was specified for the selected partition `` and QoS ``. Valid `GRES` types for this partition and QoS selection are: ``. | You have specified `GRES` type that is not compatible with this partition. | Select a valid `GRES` type from the list provided in the error message. | +| 11 | For the partition `` and QoS ``, users can only request `` GPU(s) per job. | You have requested a greater number of GPUs than are allowed for this partition and QoS. | Request fewer GPUs for your job, up to the number specified in the error message. | +| 12 | Users must specify `--ntasks` or `--mem` for all GPU partitions. | You have requested resources from a GPU partition, but did not specify the `--ntasks` or `--mem` directives. | Specify values for `--ntasks` or `--mem` in your job request. | +| 13 | You are requesting tasks/CPUs, which exceeds the maximum allowed of tasks/CPUs for GPU(s). | You have requested a greater number of CPU cores (`--ntasks` or `--ntasks` * `--cpus-per-task`) than is allowed for the specified number of GPUs. | Decrease the number of tasks/CPUs requested, or increase the number of GPUs reqeusted. | +| 14 | You are requesting `` MiB of RAM, which exceeds the maximum allowed of `` MiB of RAM for `` GPU(s). | You have requested more than the maximum allowed amount of RAM (memory) for this partition. | Request less RAM in your job submission, no more than the amount specified in the error message. | +| 15 | A partition has not been provided; specifying a partition is now required. For more information on valid partition values, please see https://curc.readthedocs.io/en/latest/clusters/alpine/alpine-hardware.html#partitions. | You have not specified a partition in your job submission; specifying a partition is required. | Specify a partition name in your job submission. Please see the following page for a list of valid partitions: https://curc.readthedocs.io/en/latest/clusters/alpine/alpine-hardware.html#partitions | +| 16 | If a list of partitions is provided, there cannot be a mix of GPU and CPU only partitions. | Your job request contains a list of both GPU- and CPU-only partitions, which cannot be mixed. | Do not mix CPU- and GPU-only partitions in your job requests. If specifying a list of partitions, do not mix partition types in the list. | +| 17 | A Quality of Service (QoS) has not been provided. Specifying a QoS is now required. For more information on valid QoS values, please see https://curc.readthedocs.io/en/latest/clusters/alpine/alpine-hardware.html#quality-of-service-qos. | You have not specified a QoS in your job submission; specifying a QoS is required. | Specify a QoS name in your job submission. Please see the following page for a list of valid QoS values: https://curc.readthedocs.io/en/latest/clusters/alpine/alpine-hardware.html#quality-of-service-qos | +| 18 | A list of QoS is currently not supported. | You have provided a comma-separated list of QoS values, which is not permitted. | Specify only one QoS value in your job submission. | +| 19 | Time has not been specified (i.e. the Slurm directive `--time`). Specifying job run time is now required. For assistance with setting run time, please email rc-help@colorado.edu. | Your have not specified a value for `--time` in your job submission. | Specify a value for time using the `--time` directive. | +| 20 | The requested runtime of the `` QoS cannot exceed `` hour(s). | You have requested more than the maximum amount of time allowed for this QoS. | Reduce the time requested for the job, or switch to a different QoS that supports longer jobs. | +| 21 | The requested runtime of the `` QoS must be greater than `` hour(s). | You have not requested enough time to meet the minimum required for this QoS. | Increase the time requested for the job, or switch to a different QoS that supports shorter jobs. | +| 22 | When requesting resources from GPU partitions, users must specify `--gres`. | You have not specified a `GRES` using the `--gres` directive, which is required on this partition. | Specify a `GRES` using the `--gres` directive. | +| 23 | If a list of GPU partitions is provided, then `GRES` must be set to `--gres=gpu:N`, where `N` is the number of GPUs. | You have provided an invalid `GRES` format while using a list of GPU partitions. | Use the `GRES` format `--gres=gpu:N`, where `N` is the number of GPUs. | + + +## Alpine and Blanca `squeue` Status and Reason Codes + +The `squeue` command details a variety of information on an active +job’s status with state and reason codes. *__Job state +codes__* describe a job’s current state in queue (e.g. pending, +completed). *__Job reason codes__* describe the reason why the job is +in its current state. + +The following tables outline a variety of job state and reason codes you +may encounter when using squeue to check on your jobs. + +### Job State Codes + +| Status | Code | Explaination | +| ------------- | :---: | ---------------------------------------------------------------------- | +| COMPLETED | `CD` | The job has completed successfully. | +| COMPLETING | `CG` | The job is finishing but some processes are still active. | +| FAILED | `F` | The job terminated with a non-zero exit code and failed to execute. | +| PENDING | `PD` | The job is waiting for resource allocation. It will eventually run. | +| PREEMPTED | `PR` | The job was terminated because of preemption by another job. | +| RUNNING | `R` | The job currently is allocated to a node and is running. | +| SUSPENDED | `S` | A running job has been stopped with its cores released to other jobs. | +| STOPPED | `ST` | A running job has been stopped with its cores retained. | + +```{seealso} +A full list of these Job State codes can be found in [Slurm’s +documentation.](https://slurm.schedmd.com/squeue.html#lbAG) +``` + +### Job Reason Codes + +| Reason Code | Explanation | +| ------------------------ | ------------------------------------------------------------------------------------------- | +| `Priority` | One or more higher priority jobs is in queue for running. Your job will eventually run. | +| `Dependency` | This job is waiting for a dependent job to complete and will run afterward. | +| `Resources` | The job is waiting for resources to become available and will eventually run. | +| `InvalidAccount` | The job’s account is invalid. Cancel the job and rerun with the correct account. | +| `InvaldQoS` | The job’s QoS is invalid. Cancel the job and rerun with the correct account. | +| `QOSGrpCpuLimit` | All CPUs assigned to your job’s specified QoS are in use; the job will run eventually. | +| `QOSGrpMaxJobsLimit` | Maximum number of jobs for your job’s QoS have been met; the job will run eventually. | +| `QOSGrpNodeLimit` | All nodes assigned to your job’s specified QoS are in use; the job will run eventually. | +| `PartitionCpuLimit` | All CPUs assigned to your job’s specified partition are in use; the job will run eventually. | +| `PartitionMaxJobsLimit` | Maximum number of jobs for your job’s partition have been met; the job will run eventually. | +| `PartitionNodeLimit` | All nodes assigned to your job’s specified partition are in use; the job will run eventually. | +| `AssociationCpuLimit` | All CPUs assigned to your job’s specified association are in use; the job will run eventually. | +| `AssociationMaxJobsLimit`| Maximum number of jobs for your job’s association have been met; the job will run eventually. | +| `AssociationNodeLimit` | All nodes assigned to your job’s specified association are in use; the job will run eventually. | + +```{seealso} +A full list of these Job Reason Codes can be found [in Slurm’s +documentation.](https://slurm.schedmd.com/squeue.html#lbAF) +``` From 875f74f55f5b1b171a4876a994b3467191f915ee Mon Sep 17 00:00:00 2001 From: John Reiland <93950341+jreiland@users.noreply.github.com> Date: Thu, 23 Jul 2026 15:52:04 -0600 Subject: [PATCH 3/4] Update index to reflect status code page name change --- docs/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/index.md b/docs/index.md index 921c1e71d..f1b1ad30e 100644 --- a/docs/index.md +++ b/docs/index.md @@ -73,7 +73,7 @@ running-jobs/job-arrays running-jobs/roce-enabled running-jobs/job-resources running-jobs/slurm-commands -running-jobs/squeue-status-codes +running-jobs/error-status-codes running-jobs/persistence1 ``` From 47aefb1385ccdc7468245ca53e6930c50d56fdd2 Mon Sep 17 00:00:00 2001 From: John Reiland <93950341+jreiland@users.noreply.github.com> Date: Sat, 1 Aug 2026 02:39:29 -0600 Subject: [PATCH 4/4] Revise job submission error and warning codes Updated error status codes to include warnings and improved formatting. --- docs/running-jobs/error-status-codes.md | 51 ++++++++++++++----------- 1 file changed, 28 insertions(+), 23 deletions(-) diff --git a/docs/running-jobs/error-status-codes.md b/docs/running-jobs/error-status-codes.md index 8ec509ed8..22ac0d252 100644 --- a/docs/running-jobs/error-status-codes.md +++ b/docs/running-jobs/error-status-codes.md @@ -1,32 +1,37 @@ -# Job Submission and Status Error and Reason Codes +# Job Submission and Status Error, Warning, and Reason Codes ## Alpine Job Submission Error Codes | **#** | **Error Message** | **Cause / Explanation** | **Resolution / Action** | | --- | --- | --- | --- | | 1 | The `` partition accepts the following QoS values: `` | You have provided a QoS value that is not supported by the requested partition. | Use a supported QoS from the list given in the error output. | -| 2 | Please modify your provided `GRES` so that the `GRES` type is specified. For the `` partition and `` QoS, valid GRES are as follows (where `N` is the number of GPUs): `` | You have not specified a `GRES` type in your provided `--gres` option. | Select a valid `GRES` type from the list provided in the error message. | -| 3 | Users must specify `--nodes` for all GPU partitions. | You have not specified a number of nodes in your job request, which is required on all GPU partitions. | Specify a number of nodes using the `--nodes=N` directive, where N is the number of nodes to request. | -| 4 | All GPU jobs are limited to 1 node. Please reschedule your job using `--nodes=1`. | You have requested more than one node (the maximum allowed) on a GPU partition. | Reschedule your job using `--nodes=1`. | -| 5 | When requesting resources on the `` partition, users must specify `--gres`. | You have not specified a `GRES` using the `--gres` directive, which is required on this partition. | Specify a `GRES` using the `--gres` directive. | -| 6 | A list of `gres` options is currently not permitted. | You have provided a comma-separated list of `GRES` options, which is not permitted. | Specify only one `GRES` option. | -| 7 | An invalid `--gres` input was provided. | You have provided an invalid `--gres` option. | Please check the spelling of your `--gres` input and try again. | -| 8 | For GPU partitions, users must use the `gres` name `gpu`. | You have specified a `gres` option other than `gpu` on a GPU partition. | Please specify `gpu` as the `gres` name. | -| 9 | Since a `GRES` type was not specified, `GRES` has been set to `--gres=`. | You did not specify a `GRES` type, so one was automatically selected. | Please specify a `gres` type (for example, `--gres=gpu:a100-40gb`) in the future. | -| 10 | An invalid `GRES` type was specified for the selected partition `` and QoS ``. Valid `GRES` types for this partition and QoS selection are: ``. | You have specified `GRES` type that is not compatible with this partition. | Select a valid `GRES` type from the list provided in the error message. | -| 11 | For the partition `` and QoS ``, users can only request `` GPU(s) per job. | You have requested a greater number of GPUs than are allowed for this partition and QoS. | Request fewer GPUs for your job, up to the number specified in the error message. | -| 12 | Users must specify `--ntasks` or `--mem` for all GPU partitions. | You have requested resources from a GPU partition, but did not specify the `--ntasks` or `--mem` directives. | Specify values for `--ntasks` or `--mem` in your job request. | -| 13 | You are requesting tasks/CPUs, which exceeds the maximum allowed of tasks/CPUs for GPU(s). | You have requested a greater number of CPU cores (`--ntasks` or `--ntasks` * `--cpus-per-task`) than is allowed for the specified number of GPUs. | Decrease the number of tasks/CPUs requested, or increase the number of GPUs reqeusted. | -| 14 | You are requesting `` MiB of RAM, which exceeds the maximum allowed of `` MiB of RAM for `` GPU(s). | You have requested more than the maximum allowed amount of RAM (memory) for this partition. | Request less RAM in your job submission, no more than the amount specified in the error message. | -| 15 | A partition has not been provided; specifying a partition is now required. For more information on valid partition values, please see https://curc.readthedocs.io/en/latest/clusters/alpine/alpine-hardware.html#partitions. | You have not specified a partition in your job submission; specifying a partition is required. | Specify a partition name in your job submission. Please see the following page for a list of valid partitions: https://curc.readthedocs.io/en/latest/clusters/alpine/alpine-hardware.html#partitions | -| 16 | If a list of partitions is provided, there cannot be a mix of GPU and CPU only partitions. | Your job request contains a list of both GPU- and CPU-only partitions, which cannot be mixed. | Do not mix CPU- and GPU-only partitions in your job requests. If specifying a list of partitions, do not mix partition types in the list. | -| 17 | A Quality of Service (QoS) has not been provided. Specifying a QoS is now required. For more information on valid QoS values, please see https://curc.readthedocs.io/en/latest/clusters/alpine/alpine-hardware.html#quality-of-service-qos. | You have not specified a QoS in your job submission; specifying a QoS is required. | Specify a QoS name in your job submission. Please see the following page for a list of valid QoS values: https://curc.readthedocs.io/en/latest/clusters/alpine/alpine-hardware.html#quality-of-service-qos | -| 18 | A list of QoS is currently not supported. | You have provided a comma-separated list of QoS values, which is not permitted. | Specify only one QoS value in your job submission. | -| 19 | Time has not been specified (i.e. the Slurm directive `--time`). Specifying job run time is now required. For assistance with setting run time, please email rc-help@colorado.edu. | Your have not specified a value for `--time` in your job submission. | Specify a value for time using the `--time` directive. | -| 20 | The requested runtime of the `` QoS cannot exceed `` hour(s). | You have requested more than the maximum amount of time allowed for this QoS. | Reduce the time requested for the job, or switch to a different QoS that supports longer jobs. | -| 21 | The requested runtime of the `` QoS must be greater than `` hour(s). | You have not requested enough time to meet the minimum required for this QoS. | Increase the time requested for the job, or switch to a different QoS that supports shorter jobs. | -| 22 | When requesting resources from GPU partitions, users must specify `--gres`. | You have not specified a `GRES` using the `--gres` directive, which is required on this partition. | Specify a `GRES` using the `--gres` directive. | -| 23 | If a list of GPU partitions is provided, then `GRES` must be set to `--gres=gpu:N`, where `N` is the number of GPUs. | You have provided an invalid `GRES` format while using a list of GPU partitions. | Use the `GRES` format `--gres=gpu:N`, where `N` is the number of GPUs. | +| 2 | Users must specify `--nodes` for all GPU partitions. | You have not specified a number of nodes in your job request, which is required on all GPU partitions. | Specify a number of nodes using the `--nodes=N` directive, where `N` is the number of nodes to request. | +| 3 | All GPU jobs are limited to 1 node. Please reschedule your job using `--nodes=1`. | You have requested more than one node (the maximum allowed) on a GPU partition. | Reschedule your job using `--nodes=1`. | +| 4 | A list of `gres` options is currently not permitted. | You have provided a comma-separated list of `GRES` options, which is not permitted. | Specify only one `GRES` option. | +| 5 | An invalid `--gres` input was provided. | You have provided an invalid `--gres` option. | Please check the spelling of your `--gres` input and try again. | +| 6 | For GPU partitions, users must use the `gres` name `gpu`. | You have specified a `gres` option other than `gpu` on a GPU partition. | Please specify `gpu` as the `gres` name. | +| 7 | An invalid `GRES` type was specified for the selected partition `` and QoS ``. Valid `GRES` types for this partition and QoS selection are: ``. | You have specified `GRES` type that is not compatible with this partition. | Select a valid `GRES` type from the list provided in the error message. | +| 8 | For the QoS ``, users can only request `` GPU(s) of type `` per job. | You have requested a greater number of GPUs than are allowed for this partition and QoS. | Request fewer GPUs for your job, up to the number specified in the error message. | +| 9 | Users must specify `--ntasks` or `--mem` for all GPU partitions. | You have requested resources from a GPU partition, but did not specify the `--ntasks` or `--mem` directives. | Specify values for `--ntasks` or `--mem` in your job request. | +| 10 | You are requesting `` tasks, which exceeds the maximum allowed of `` tasks for `` GPU(s) of type ``. | You have requested a greater number of tasks (`--ntasks`) than is allowed for the specified number of GPUs. | Decrease the number of tasks requested, or increase the number of GPUs reqeusted. | +| 11 | You are requesting `` CPUs, which exceeds the maximum allowed of `` CPUs for `` GPU(s) of type ``. | You have requested a greater number of CPUs (`--ntasks` * `--cpus-per-task`) than is allowed for the specified number of GPUs. | Decrease the number of CPUs requested, or increase the number of GPUs reqeusted. | +| 12 | You are requesting `` MiB of RAM, which exceeds the maximum allowed of `` MiB of RAM for `` GPU(s) of type ``. | You have requested more than the maximum allowed amount of RAM (memory) for this partition. | Request less RAM in your job submission, no more than the amount specified in the error message. | +| 13 | A partition has not been provided, specifying a partition is now required. | You have not specified a partition in your job submission; specifying a partition is required. | Specify a partition name in your job submission. Please see the following page for a list of valid partitions: https://curc.readthedocs.io/en/latest/clusters/alpine/alpine-hardware.html#partitions | +| 14 | If a list of partitions is provided, there cannot be a mix of GPU and CPU only partitions. | Your job request contains a list of both GPU- and CPU-only partitions, which cannot be mixed. | Do not mix CPU- and GPU-only partitions in your job requests. If specifying a list of partitions, do not mix partition types in the list. | +| 15 | A Quality of Service (QoS) has not been provided. Specifying a QoS is now required. | You have not specified a QoS in your job submission; specifying a QoS is required. | Specify a QoS name in your job submission. Please see the following page for a list of valid QoS values: https://curc.readthedocs.io/en/latest/clusters/alpine/alpine-hardware.html#quality-of-service-qos | +| 16 | A list of QoS is currently not supported. | You have provided a comma-separated list of QoS values, which is not permitted. | Specify only one QoS value in your job submission. | +| 17 | Time has not been specified (i.e. the Slurm directive `--time`). Specifying job run time is now required. | You have not specified a value for `--time` in your job submission. | Specify a value for time using the `--time` directive. For assistance with setting run time, please submit a [Support Request Form](https://colorado.service-now.com/req_portal?id=ucb_sc_rc_form). | +| 18 | The requested runtime of the `` QoS cannot exceed `` hour(s). | You have requested more than the maximum amount of time allowed for this QoS. | Reduce the time requested for the job, or switch to a different QoS that supports longer jobs. | +| 19 | The requested runtime of the `` QoS must be greater than `` hour(s). | You have not requested enough time to meet the minimum required for this QoS. | Increase the time requested for the job, or switch to a different QoS that supports shorter jobs. | +| 20 | When requesting resources from GPU partitions, users must specify `--gres`. | You have not specified a `GRES` using the `--gres` directive, which is required on this partition. | Specify a `GRES` using the `--gres` directive. | +| 21 | If a list of GPU partitions is provided, then `GRES` must be set to `--gres=gpu:N`, where `N` is the number of GPUs. | You have provided an invalid `GRES` format while using a list of GPU partitions. | Use the `GRES` format `--gres=gpu:N`, where `N` is the number of GPUs. | + +## Alpine Job Submission Warning Codes + +| **#** | **Warning Message** | **Cause / Explanation** | **Resolution / Action** | +| --- | --- | --- | --- | +| 1 | Please modify your provided `GRES` so that the `GRES` type is specified. For the `` partition and `` QoS, valid `GRES` are as follows (where `N` is the number of GPUs): `` | You have not specified a `GRES` type in your provided `--gres` option. | Select a valid `GRES` type from the list provided in the error message. | +| 2 | Since a `GRES` type was not specified, `GRES` has been set to `--gres=.` | You did not specify a GRES type, so one was automatically selected. | Please specify a `gres` type (for example, `--gres=gpu:a100-40gb`) in the future. | ## Alpine and Blanca `squeue` Status and Reason Codes