- 06 Apr, 2015 6 commits
-
-
Morris Jette authored
* Add "TopologyParam" configuration parameter. Optional value of "dragonfly" is supported. * select/linear: Add dragonfly topology support * select/cons_res: Add dragonfly topology support
-
Morris Jette authored
We plan to duplicate partially duplicate a function and replaced that function name in logs with "__func__" for better code re-use.
-
Morris Jette authored
No changes to the test logic
-
Brian Christiansen authored
Conflicts: doc/man/man1/sacct.1 doc/man/man1/srun.1 src/sacct/sacct.h
-
Brian Christiansen authored
Bug 1578
-
David Bigagli authored
-
- 03 Apr, 2015 8 commits
-
-
Morris Jette authored
-
Morris Jette authored
-
Morris Jette authored
-
Morris Jette authored
-
Morris Jette authored
-
Morris Jette authored
-
Matthieu Hautreux authored
-
Morris Jette authored
-
- 02 Apr, 2015 11 commits
-
-
Morris Jette authored
-
Nicolas Joly authored
-
David Bigagli authored
-
Nicolas Joly authored
-
David Bigagli authored
-
Morris Jette authored
-
Morris Jette authored
-
Morris Jette authored
-
Morris Jette authored
-
Samuel Senoner authored
-
Morris Jette authored
-
- 01 Apr, 2015 15 commits
-
-
Brian Christiansen authored
Bug 1550
-
David Bigagli authored
-
David Bigagli authored
-
David Bigagli authored
their own jobs.
-
David Bigagli authored
-
Brian Christiansen authored
-
Brian Christiansen authored
Bug 1469
-
David Bigagli authored
-
Morris Jette authored
This seems to apply only to Cray/ALPS systems. This partially reverts commit 5fc68cae It also adds a new check for NULL job_ptr
-
Morris Jette authored
_entity_add_data() in src/common/entity.c defined as "static" to avoid confusion with same function name in src/common/layouts_mgr.c _entity_get_node_walkfunc() in src/common/entity.c defined as "static" Removed redundant set of "rc" variable _layouts_autoupdate_layout_if_allowed(), src/common/layouts_mgr.c Initialized variable "rc" in _layouts_read_state(), src/common/layouts_mgr.c in case the named file does not exist (stat() returns an error) The CLANG tool reported a possible error in _autoupdate_layout_tree(), src/common/layouts_mgr.c in the event that xtree_node_get_data() returns a NULL value and that pointer is used later in the function for "cnode->entity". I added "return 1" if xtree_node_get_data() returns NULL, but am not yet sure if that is the correct action. The CLANG tool reported possible errors related to a NULL value pointer in s_p_parse_pair_with_op(), src/common/parse_config.c which have been fixed.
-
Matthieu Hautreux authored
-
Matthieu Hautreux authored
-
Matthieu Hautreux authored
-
Matthieu Hautreux authored
Having MAX_PREFIX_CNT to 1k limits the number of elements that can be expressed using expressions like node[1-1025].ib[0] to 1024. As 64k is the max number of nodes that can be handled by Slurm, increase that value to 64k in order to be able to express at least that number of elements using a[x]b[y] when y is the same value for all the elements. Note: also required by the layouts parsing logic when parsing float values in expressions like : 'Entity=node[1-64000] FloatKey=[1-64000].[0]'
-
Matthieu Hautreux authored
layouts plugins inheritances among entities KVs like KEYSPEC_UPDATE_CHILDREN_SUM (see layouts_mgr.h) are now fully managed by the layouts manager. An extra third stage is added while loading the configuration and state informations during startup in order to automatically update the layouts entities KVs based on the relationships defined in the plugin among the keys. The third stage is executed right after the second one that is in charge of establishing the relations among the entities. When an update is performed using the API laouts_update_layout call, the autoupdate logic is also applied. Note that a layout plugin must explicitely ask for autoupdate support by the layouts manager using the autoupdate field of its layouts_plugin_spec_t internal structure 'plugin_spec'. layouts API calls using the push/pull logic also leverage the autoupdate mechanism. Note that for now, the autoupdate is "full" whenever it is called. Improvements should be considered in the future to improve the performance of the logic when possible, especially in push/pull contexts.
-