- 10 Mar, 2011 4 commits
-
-
Moe Jette authored
-
Moe Jette authored
-
Danny Auble authored
-
Moe Jette authored
Both parameters will be supported for now.
-
- 09 Mar, 2011 8 commits
-
-
-
Danny Auble authored
Fix for sview started on a non-bluegene system to pick colors correctly when talking to a real bluegene system.
-
Moe Jette authored
Use PREFIX instead to avoid build errors from multiple installation specifications.
-
-
Moe Jette authored
reservation may use the licenses associated with it plus any compute nodes. Otherwise the job is limited to the compute nodes associated with the reservation.
-
Moe Jette authored
-
Danny Auble authored
-
Danny Auble authored
-
- 08 Mar, 2011 16 commits
-
-
Danny Auble authored
-
Danny Auble authored
-
Danny Auble authored
-
Danny Auble authored
-
Danny Auble authored
-
-
Moe Jette authored
-
Danny Auble authored
-
Danny Auble authored
-
Moe Jette authored
a full midplane on BlueGene computers. Treat cnodes as liceses which can be reserved and are consumed by jobs.
-
Moe Jette authored
Perl can not build if both are set.
-
Moe Jette authored
-
Moe Jette authored
This removes a redundant test for NODE_RESUME if the old state was NODE_STATE_UNKNOWN, and an unreached break.
-
Moe Jette authored
Just a suggestion, also updates comment text.
-
Danny Auble authored
-
Danny Auble authored
-
- 07 Mar, 2011 6 commits
- 06 Mar, 2011 6 commits
-
-
Moe Jette authored
Since "aprun" is used on Cray instead of srun, the --no-shell option does not make any difference: with or without this option, the ALPS reservation is made, and since it is confirmed using the SID of the current shell, aprun will run even if the BASIL_RESERVATION_ID is not set. NB: the patch aborts with an error message. If deciding to turn this into a warning, and continue processing, opt.no_shell should be disabled, since otherwise interactive mode (and thus job control) is disabled.
-
Moe Jette authored
return_hostlist is not populated in validate_nodes_via_front_end, hence never printed out.
-
Moe Jette authored
This * removes outdated and no longer applicable comments regarding consecutive node numbering (dating from an earlier revision); * fixes a typo and clarifies condition on XT/SeaStar systems.
-
Moe Jette authored
This fixes an inconsistency: time_t is not necessarily u32, use a separate routine to parse the absolute value and use proper time_t type. Also tidied up code where possible.
-
Moe Jette authored
This reduces the amount of error text printed on failure of do_basil_release(): * parameter failures are caught by the existing calls to error(), * internal (ALPS) errors are printed by basil_release(), * there is no need to return additional error information via errno, * functions calling select_g_job_fini() just interpret the error, but no further action is taken, hence it is not necessary to indicate failure more than once. The following shows how setting SLURM_ERROR/errno produces unnecessarily long error text: [2011-02-09T18:19:51] debug2: Processing RPC: REQUEST_CANCEL_JOB_STEP uid=21215 [2011-02-09T18:19:51] error: PERMANENT ALPS BACKEND error: ALPS error: apsched: No entry for resId 286 [2011-02-09T18:19:51] error: releasing ALPS resId 286 for JobId 2940 FAILED with -5 [2011-02-09T18:19:51] error: select_g_job_fini(2940): No error With the patch, only [2011-02-09T18:19:51] error: PERMANENT ALPS BACKEND error: ALPS error: apsched: No entry for resId 286 would be printed, which is sufficient to diagnose the problem (resId 286 had been terminated by ALPS internally, after not receiving a confirmation quickly enough).
-
Moe Jette authored
This introduces a function which first checks prior to releasing an ALPS reservation if there are any application APIDs still associated with it. If there are, it attempts to kill those presumably stray job steps using the Cray apkill(1) binary. In most cases this is sufficient to successfully release the reservation. If on the other hand the reservation is formally released while still APIDs are associated with it, the reservation will remain (and its resources not released back) until the associated applications (APIDs) have terminated. Use of this function is restricted to cleaning up orphaned reservations. When trying to also use this for normal (non-abortive) job termination, it resulted in error messages, where the APID was still associated with the reservation, but had just shortly before been released, i.e. it generated false positives. The patch passed the following test case: 1. set up an ALPS reservation: salloc -N 12 2. spawn long-running apruns: for i in {1..13};do aprun sleep 3600&done 3. (in a different window) kill -9 $(pidof salloc) scancel -u $USER 4. after the job had completed within slurm, the following cleanup happened: [2011-03-05T13:19:07] debug2: purge_old_job: purged 1 old job records [2011-03-05T13:19:37] debug: BASIL 3.1 INVENTORY: 128/176 batch nodes available [2011-03-05T13:19:37] debug: ALPS: 12 node(s) still held [2011-03-05T13:19:37] error: orphaned ALPS reservation 147, trying to remove [2011-03-05T13:19:37] error: apkill live apid 168913 of ALPS resId 147 [2011-03-05T13:19:37] error: apkill live apid 168912 of ALPS resId 147 [2011-03-05T13:19:37] error: apkill live apid 168911 of ALPS resId 147 [2011-03-05T13:19:37] error: apkill live apid 168910 of ALPS resId 147 [2011-03-05T13:19:37] error: apkill live apid 168909 of ALPS resId 147 [2011-03-05T13:19:37] error: apkill live apid 168908 of ALPS resId 147 [2011-03-05T13:19:37] error: apkill live apid 168907 of ALPS resId 147 [2011-03-05T13:19:37] error: apkill live apid 168906 of ALPS resId 147 [2011-03-05T13:19:37] error: apkill live apid 168905 of ALPS resId 147 [2011-03-05T13:19:37] error: apkill live apid 168904 of ALPS resId 147 [2011-03-05T13:19:37] error: apkill live apid 168903 of ALPS resId 147 [2011-03-05T13:19:37] error: apkill live apid 168902 of ALPS resId 147 ==> Subsequently, reservation 147 was released, and a new salloc could be granted.
-