1. 10 Jul, 2015 1 commit
  2. 09 Jul, 2015 1 commit
    • Morris Jette's avatar
      Bug fixes in powercapping logic · 44619ea0
      Morris Jette authored
      Changed spaces to tabs at start of lines.
      Minor changes to some formatting.
      Added the new files to the RPM (slurm.spec file).
      Prevent memory leak of "l_name" variable if which_power_layout()
          function is called more than once.
      Initialize "cpufreq" variable in powercap_get_cpufreq() function.
      Array "tmp_max_watts_dvfs" could be NULL and used if "max_watts_dvfs" variable is
          NULL in powercap_get_node_bitmap_maxwatts_dvfs()
      Variable "tmp_pcap_cpu_freq" could be used with uninitialized value in function
          _get_req_features()
      Variable "tmp_max_watts" could be used with uninitialized value in function
          _get_req_features()
      Array "tmp_max_watts_dvfs" could be used with uninitialized value in function
          _get_req_features()
      Array "allowed_freqs" could be NULL and used if "node_record_count" variable is
          zero in powercap_get_job_nodes_numfreq()
      Overwriting a memory buffer header (especially with different data types) is
          just asking for something bad to happen. This...
      44619ea0
  3. 08 Jul, 2015 3 commits
  4. 07 Jul, 2015 6 commits
  5. 06 Jul, 2015 2 commits
    • Morris Jette's avatar
      scheduler/backfill enhancements · edfbabe6
      Morris Jette authored
      Backfill scheduler now considers OverTimeLimit and KillWait configuration
      parameters to estimate when running jobs will exit. Initially the job's
      end time is estimated based upon it's time limit. After the time limit
      is reached, the end time estimate is based upon the OverTimeLimit and
      KillWait configuration parameters.
      bug 1774
      edfbabe6
    • Morris Jette's avatar
      Add backfill scheduler timeout · 7e944220
      Morris Jette authored
      Backfill scheduler: The configured backfill_interval value (default 30
          seconds) is now interpretted as a maximum run time for the backfill
          scheduler. Once reached, the scheduler will build a new job queue and
          start over, even if not all jobs have been tested.
      bub 1774
      7e944220
  6. 02 Jul, 2015 2 commits
  7. 01 Jul, 2015 2 commits
    • Brian Christiansen's avatar
      Show job in sacct when step's cpus are different from job allocation. · 0f8e7338
      Brian Christiansen authored
      When submitting a job with srun -n# the job may be allocated more than # because
      the job was given the whole core or socket (eg. CR_CORE, CR_SOCKET). sacct
      showed only what the step used and not the allocation. This commit shows the job
      and the step if job and step cpus are different.
      0f8e7338
    • Morris Jette's avatar
      Add TRES support to sreport command · b860ed8e
      Morris Jette authored
      Major re-write of the sreport command to support --tres job option
      and permit users to select specific tracable resources to generate
      reports for. For most reports, each TRES is listed on a separate
      line of output with its name. The default TRES type is "cpu" to
      minimize changes to output.
      b860ed8e
  8. 30 Jun, 2015 2 commits
  9. 29 Jun, 2015 2 commits
  10. 26 Jun, 2015 2 commits
  11. 25 Jun, 2015 2 commits
  12. 24 Jun, 2015 2 commits
  13. 23 Jun, 2015 1 commit
  14. 22 Jun, 2015 3 commits
    • Morris Jette's avatar
      Advanced reservation fixes · a6454176
      Morris Jette authored
      Updates of existing bluegene advanced reservations did not work at all.
      Some multi-core configurations resulting in an abort due to creating
        core_bitmaps for the reservation that only had one bit per node rather
        than one bit per core.
      These bugs were introduced in commit 5f258072
      a6454176
    • David Bigagli's avatar
      Update NEWS · c8545598
      David Bigagli authored
      c8545598
    • David Bigagli's avatar
      Update NEWS · 38007f9b
      David Bigagli authored
      38007f9b
  15. 19 Jun, 2015 1 commit
  16. 15 Jun, 2015 1 commit
  17. 12 Jun, 2015 3 commits
  18. 11 Jun, 2015 1 commit
  19. 10 Jun, 2015 1 commit
  20. 09 Jun, 2015 2 commits
    • David Bigagli's avatar
      Search for user in all groups · 93ead71a
      David Bigagli authored
      93ead71a
    • Morris Jette's avatar
      Fix scheduling inconsistency with GRES · e1a00772
      Morris Jette authored
      1. I submit a first job that uses 1 GPU:
      $ srun --gres gpu:1 --pty bash
      $ echo $CUDA_VISIBLE_DEVICES
      0
      
      2. while the first one is still running, a 2-GPU job asking for 1 task per node
      waits (and I don't really understand why):
      $ srun --ntasks-per-node=1 --gres=gpu:2 --pty bash
      srun: job 2390816 queued and waiting for resources
      
      3. whereas a 2-GPU job requesting 1 core per socket (so just 1 socket) actually
      gets GPUs allocated from two different sockets!
      $ srun -n 1  --cores-per-socket=1 --gres=gpu:2 -p testk --pty bash
      $ echo $CUDA_VISIBLE_DEVICES
      1,2
      
      With this change #2 works the same way as #3.
      bug 1725
      e1a00772