No. The code would need to be changed. These strings can get really long so I'm not sure that you would always want the entire string.
On April 27, 2015 10:01:35 PM PDT, Jun-Xian Leong <[email protected]> wrote: >Hi Moe, > >Thanks very much for the help! > >If we wanted the default behaviour to be to always print the whole >string, >is there somewhere in the ctld setup that we could set this variable >(to >some large number) as a default? > >Cheers, >-JX > > > > >On 28 April 2015 at 12:28, Moe Jette <[email protected]> wrote: > >> >> Set an environment variable SLURM_BITSTR_LEN to the maximum string >length >> that you want. >> >> >> Quoting Jun-Xian Leong <[email protected]>: >> >>> Hi devs, >>> >>> I'm working on an external app which accesses the API for Slurm >v14.11. >>> >>> Have noticed that the char* array_task_str returned in >slurm_job_info_t is >>> often truncated when you have large lists of nonsequential jobs. >>> eg: submitted arrays: >>> >>> >4020,4045,4070,4095,4120,4145,4170,4195,4220,4245,4270,4295,4320,4345,4370,4395,4420,4445,4470,4495,4520,4545,4570,4595 >>> but array_task_str returns >>> 4070,4095,4120,4145,4170,4195,4220,4245,4270,4295,4320,4345,... >>> >>> Is there any method to obtain the full list of tasks actually >scheduled >>> via >>> the slurm_job_info_t struct? >>> >>> Cheers, >>> -JX >>> >> >> >> -- >> Morris "Moe" Jette >> CTO, SchedMD LLC >> Commercial Slurm Development and Support >> -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
