Initially job mem limits were tested at submission time through
_validate_min_mem_partition() -> _valid_pn_min_mem(), but not tested
again at scheduling time, thus leading to jobs incorrectly being scheduled
against partitions where the job exceeded their MaxMemPer* limit
(which can in turn be inherited from the system wide limit too).

NOTE: New WAIT_PN_MEM_LIMIT job_state_reason enum component added to support
this new waiting reason.

Bug 2291.

checked on submit.

This only mattered when submitting a job to multiple partitions.

Bug 4066

on node 0.

Bug 4035

Add the xassert() that the inline version has to _remove_job_hash().

To avoid a reliance on the slurm.conf file (as this command is
designed to help you construct said file) the path to check the
space was hard-coded as /tmp. But, if TmpFS is meant to be elsewhere
we'd emit the wrong value here.

Bug 3272.

A lot of slurmdbd operations are authenticated by the accounting_storage
plugin, rather than in slurmdbd. To allow the drop_priv flag to work it
must be checked in is_user_min_admin_level() in addition to the various
functions in proc_req.c .

If SLURM_TESTSUITE_DROP_PRIV is defined (regardless of the value),
set SLURM_DROP_PRIV in the message header so the slurmctld/slurmdbd
will treat the request as if issued from an unprivileged user account.

Bug 4080.

See prior commit da1d3858.

Bug 4080.

This reverts commit 46a46b91.

This reverts commit a2134b14.

This reverts commit 29fe710d.

This reverts commit 47dad9e8.

On second thought, we should be using these or quite similar functions.

This reverts commit a44ef130.

Will be removed in 17.11, and 'sgj_job' is a typo anyways.

A lot of slurmdbd operations are authenticated by the accounting_storage
plugin, rather than in slurmdbd. To allow the drop_priv flag to work it
must be checked in is_user_min_admin_level() in addition to the various
functions in proc_req.c .

The drop_priv symbol needs to be accessible from common_as.c,
which is compiled in with the accounting_storage/mysql plugin.

Since that plugin can run in slurmdbd, or directly from slurmctld and
the user commands, the only way to get drop_priv there consistently
is to move the declaration to some common ground behind all of them.

Rather than expose this throughout, just explicitly import it with
'extern' in the appropriate locations.

If SLURM_TESTSUITE_DROP_PRIV is defined (regardless of the setting),
set SLURM_DROP_PRIV in the message header so the slurmctld will treat
the request as if issued from an unprivileged user account.

Bug 4080.

See prior commit da1d3858.

Bug 4080.

Handling is enabled only in development builds. When set in the message
header, a thread-local variable in slurmctld is set to force the auth
functions (validate_slurm_user() et al) to treat the user as unpriviledge.

Designed to be used along with the testsuite at a later point in time, such
that tests can validate user access restrictions without needing access to
alternate accounts (since the testsuite is usually run as SlurmUser or at
least an Admin to validate a lot of administrative components).

Bug 4080.

Missed in commit 538bae4c.

Add _validate_slurm_user(), _validate_super_user(), _validate_operator()
all modeled after their equivalents in slurmctld.

Convert proc_rec.c over to using them instead of repeated blocks of code.

unsupported core-based reservations.

- fixed the compatibility check
- added a search in the additional path '/opt/ucx'

Signed-off-by: Boris Karasev <karasev.b@gmail.com>

Signed-off-by: Artem Polyakov <artpol84@gmail.com>

Add new performance debugging feature to pmix plugin that allows to
measure plain collectives performance on selected message sizes.
This functionality is similar to a ping-pong feature.

Performance results for existing point-to-point modes:

size    sapi            dtcp            ducx
1       0.002319442     0.000492334     0.000135243
2       0.002318223     0.000453552     0.000137356
4       0.00227046      0.00045832      0.000137117
8       0.002342675     0.000463539     0.000136455
16      0.00235131      0.000481208     0.00013619
32      0.002333058     0.000562986     0.000140756
64      0.002456691     0.000883791     0.000142574
128     0.002953556     0.001326429     0.000142336
256     0.003892236     0.002324766     0.000161224
512     0.006044123     0.004371988     0.000177675
1024    0.010324001     0.008485476     0.000224325
2048    0.018556118     0.016488896     0.000347243
4096    0.035331223     0.032744778     0.000481764
8192    0.06957123      0.065519465     0.001194106
16384   0.137925333     0.130130662     0.002544668
32768   0.272100422     0.259290563     0.009916888
65536   0.543431362     0.486692217     0.012841119

Signed-off-by: Artem Polyakov <artpol84@gmail.com>

Signed-off-by: Artem Polyakov <artpol84@gmail.com>

Signed-off-by: Artem Polyakov <artpol84@gmail.com>

Signed-off-by: Artem Polyakov <artpol84@gmail.com>

There were segmentation faults because of double free of a pending
list when UCX comonent was trying to connect multiple times.

Signed-off-by: Artem Polyakov <artpol84@gmail.com>