- 03 Dec, 2012 5 commits
-
-
https://github.com/SchedMD/slurmjette authored
-
jette authored
-
Morris Jette authored
-
jette authored
-
jette authored
This bug was introduced on Friday and fails to address an environment variable not being set
-
- 01 Dec, 2012 4 commits
-
-
Morris Jette authored
-
Morris Jette authored
-
Morris Jette authored
-
Morris Jette authored
-
- 30 Nov, 2012 12 commits
-
-
https://github.com/SchedMD/slurmjette authored
-
jette authored
-
Danny Auble authored
-
Danny Auble authored
-
Danny Auble authored
-
Danny Auble authored
-
Danny Auble authored
-
Danny Auble authored
on them. This should only happen in extreme conditions.
-
Danny Auble authored
-
Danny Auble authored
-
Phil Eckert authored
-
Morris Jette authored
-
- 29 Nov, 2012 18 commits
-
-
https://github.com/SchedMD/slurmjette authored
-
jette authored
And the user allocation tries to bind to sockets
-
Danny Auble authored
with associations get the deleted associations as well.
-
jette authored
-
Danny Auble authored
-
Danny Auble authored
-
Francois Diakhate authored
request resources that reach a 'Max' limit.
-
jette authored
-
Morris Jette authored
-
Morris Jette authored
-
Yiannis Georgiou authored
this is happening because the energy status MSR registers for Package: "MSR_PKG_ENERGY_STATUS" and DRAM: "MSR_DRAM_ENERGY_STATUS" are counted on 32 bit ( the MSRs are 64bit wide) and they wrap around every few minutes. for info check out the attached screenshot of the Intel's doc or here for Intel's complete doc: http://download.intel.com/products/processor/manual/325384.pdf
-
Danny Auble authored
-
Danny Auble authored
-
Danny Auble authored
user mark the state canceled instead of completed.
-
Morris Jette authored
-
Danny Auble authored
so it gets sent again. This isn't a major problem since the start will happen when the job ends, but this does make things cleaner.
-
Morris Jette authored
-
Morris Jette authored
-
- 28 Nov, 2012 1 commit
-
-
Danny Auble authored
-