- 10 Apr, 2019 5 commits
-
-
Dominik Bartkiewicz authored
Bug 6807.
-
Alejandro Sanchez authored
==8640== Thread 5 bckfl: ==8640== Syscall param openat(filename) points to unaddressable byte(s) ==8640== at 0x4A81D0E: open (open64.c:48) ==8640== by 0x5934ABB: _update_job_env (burst_buffer_cray.c:3338) ==8640== by 0x5934ABB: bb_p_job_begin (burst_buffer_cray.c:3962) ... ==8640== Address 0x6b96120 is 16 bytes inside a block of size 61 free'd ==8640== at 0x48369AB: free (vg_replace_malloc.c:530) ==8640== by 0x49D4873: slurm_xfree (xmalloc.c:244) ==8640== by 0x490C317: free_command_argv (run_command.c:249) ==8640== by 0x5934A5C: bb_p_job_begin (burst_buffer_cray.c:3947) ... ==8640== Block was alloc'd at ==8640== at 0x4837B65: calloc (vg_replace_malloc.c:752) ==8640== by 0x49D4566: slurm_xmalloc (xmalloc.c:87) ==8640== by 0x49D4B67: makespace (xstring.c:103) ==8640== by 0x49D4C91: _xstrcat (xstring.c:134) ==8640== by 0x49D4ECF: _xstrfmtcat (xstring.c:280) ==8640== by 0x593497C: bb_p_job_begin (burst_buffer_cray.c:3936) ... Bug 6807.
-
Doug Jacobsen authored
Bug 6807.
-
Doug Jacobsen authored
Bug 6807.
-
Doug Jacobsen authored
Bug 6807.
-
- 05 Apr, 2019 6 commits
-
-
Alejandro Sanchez authored
-
Ben Roberts authored
Updated ControlAddr to point to 127.0.0.1 rather than 123.4.5.6 Bug 6794
-
Ben Roberts authored
Bug 6768.
-
Alejandro Sanchez authored
-
Michael Hinton authored
Bug 6718.
-
Alejandro Sanchez authored
Bug 6791.
-
- 03 Apr, 2019 4 commits
-
-
Danny Auble authored
-
Alejandro Sanchez authored
This prevents rebuilding a job's dependency string when it has at least one invalid (never satisfied) dependency, no matter if such invalid dependency has already been purged (after MinJobAge) or not. This can be useful to track down the culprit invalid dependencies even after they are gone from ctld's in-memory job list. The flag is cleared upon a successful job dependency update or after another job in the dependency list has been satisfied if such list is composed with the '?' symbol (OR'ed). Bug 5851.
-
Alejandro Sanchez authored
Job dependencies separated by "?" (OR'ed) should make the dependant job be independent as soon as any of the dependencies are resolved to be satisfied. Without this patch, if an invalid (non satisfiable) dependency was resolved before a satisfiable one, then the dependant job would never become independent, even after the satisfiable one got eventually resolved. Bug 5851.
-
Alejandro Sanchez authored
No functional change, just preparement for a following commit with an actual fix. Bug 5851.
-
- 31 Mar, 2019 3 commits
-
-
Brian Christiansen authored
Continuation of 2764f3fd Bug 6589
-
Brian Christiansen authored
Continuation of 9a243a1a Bug 6592
-
Brian Christiansen authored
-
- 27 Mar, 2019 1 commit
-
-
Dominik Bartkiewicz authored
Bug 6750.
-
- 26 Mar, 2019 2 commits
-
-
Alejandro Sanchez authored
Bug 6710.
-
Marshall Garey authored
Bug 6590.
-
- 25 Mar, 2019 1 commit
-
-
Albert Gil authored
Bug 6680
-
- 22 Mar, 2019 2 commits
-
-
Alejandro Sanchez authored
-
Marshall Garey authored
With schedulerparameters=defer and prolog scripts and/or spank plugins that take some time, jobs weren't starting within 2 seconds that tests 2.18 and 2.19 expected, causing these tests to fail. Bug 6670.
-
- 21 Mar, 2019 3 commits
-
-
Tim Wickberg authored
-
Tim Wickberg authored
IMO, the test as is currently designed is not representative of an actual rpmbuild against a production released tarball, and thus should not be relied on. Using --nodeps masks a lot of potential errors with the spec file. It has been disabled on Ubuntu systems for months, broken on master for longer, and thus I am discarding it now. Bug 4411, 6281.
-
Marshall Garey authored
Change to %pJ identifier while here and merge different partition priorities into a single log message line. Bug 6663.
-
- 20 Mar, 2019 5 commits
-
-
Alejandro Sanchez authored
Bug 6723
-
Albert Gil authored
Regression from enhancement 4506. Bug 6680
-
Danny Auble authored
Bug 6662
-
Alejandro Sanchez authored
Previously the state reason could remain as WAIT_NO_REASON even after backfill evaluation. This should improve system feedback/responsiveness user perception. Bug 6594.
-
Brian Christiansen authored
Continuation of 69d78159 Bug 6500
-
- 19 Mar, 2019 2 commits
-
-
Danny Auble authored
Issue was from ade9101e. The problem was an over simplified if statement which when ran multiple times would set the start time incorrectly. Bug 6697
-
Alejandro Sanchez authored
Even if main scheduler doesn't allocate resources for hetjobs, the queue list should be composed by all types of jobs. Otherwise, lower priority regular jobs could be allocated resources by main scheduler while higher priority hetjobs are waiting for a backfill cycle. Bug 6593.
-
- 15 Mar, 2019 2 commits
-
-
Tim Wickberg authored
-
Matt Ezell authored
Bug 6679
-
- 13 Mar, 2019 1 commit
-
-
Alejandro Sanchez authored
Instruct the backfill scheduler to attempt to start a heterogeneous job as soon as all of its components are determined able to do so. Bug 5579.
-
- 12 Mar, 2019 3 commits
-
-
Danny Auble authored
-
Danny Auble authored
This could probably be extended to give back sockets and cores and such, but at this moment I really only needed how many threads to deal with and total cpus.
-
Dominik Bartkiewicz authored
There are at least two points where this can return a false positive error message which can be confusing for users. Continuation dc583bd1 Bug 6437
-