Hi,
can we see what script is broken? You may want to review #991 to get
the full picture.
On 03/05/2015 09:19 AM, Pär Lindfors wrote:
Manu Thambi <[email protected]> writes:
The following commit (which is included in version 14.11.4) seems to
make
stdout buffered when --unbuffered is passed in, which seems wrong.
...
"seems wrong" is an understatement. I honestly thought I did not read
your e-mail correctly the first time.
This is completely messed up. Please SchedMD, commit
064cdb5eb6ea95ca23b1d5118b96dd04aa4c7e06 needs to be reverted!
If no option like this had existed before, then due to the principle of
least surprise it would be quite bad to name it "--unbuffered" when what
it does is to set line buffered output.
Now the situation is a lot worse. The -u/--unbuffered option to srun
have been around for more than 10 years (added in commit 159e591b,
2003-04-08, slurm 0.2.0) and have always set stdout to be unbuffered. In
14.11 it changes to do the opposite, breaking any job script or utility
made during those years that specify "srun -u" because they actually
need unbuffered stdout.
We have such scripts, and I have just verified that they are indeed
broken on Slurm 14.11. We just took our first cluster running 14.11 into
production this week, so probably not many users have run into this yet.
Regards,
Pär Lindfors, NSC
--
Thanks,
/David/Bigagli
www.schedmd.com
