Bug 6739

Bug 6785.

Bug 6608.

Bug 6807.

==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.

Bug 6807.

Bug 6807.

Bug 6807.

Bug 6791.

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.

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.

Bug 6750.

Bug 6710.

Change to %pJ identifier while here and merge different partition
priorities into a single log message line.

Bug 6663.

Bug 6723

Regression from enhancement 4506.

Bug 6680

Bug 6662

Previously the state reason could remain as WAIT_NO_REASON even after
backfill evaluation. This should improve system feedback/responsiveness
user perception.

Bug 6594.

Continuation of 69d78159

Bug 6500

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

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.

Bug 6679

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.

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

Backport of 21b9a39b

Bug 6625

Print error: for each new line.

Bug 6142

Bug 6142

Bug 6584

response_cluster_rec stored a pointer to data in the controller config
that gets freed when the controller is reconfigured.

Bug 6584

This should never happen, but is a nice safeguard.

Bug 6566

Bug 6612

All of the buffers are 24 characters, require the input string is
less than 23 characters and null combined to be parsed.

Remove regression added in b9699c2f

Bug 6636.

What was happening in a maintenance reservation was every 5 seconds
the slurmctld was sending a message to the slurmdbd telling it the
node's down/drain state was in a maintenance state as well.  We really
only needed to know about this once.

Bug 6487

(DRAIN+MAINT+IDLE) Before it would just print MAINT
Bug 6487

Bug 4296

to avoid having to send alias list for cloud nodes that exist in DNS.
This is especially important for large cloud environments (e.g.
thousands of nodes) as the alias list environment will be too large for
execve().

Bug 6589