I'm not aware of any changes in this area. Please send a patch if you work on this.
Quoting Michael Gutteridge <[email protected]>: > > Hi all > > Running into an interesting issue with exporting environment > variables. I'm still on 2.3.5, but I wasn't able to locate anything > in changelogs that suggests behavior that's been fixed. > > Anyway- I'm passing parameters to scripts using environment variables: > > foo=bar bar=baz sbatch --export=foo,bar -J myname myscript.sh > > foo and bar are being set properly, but the SLURM environment variable > "SLURM_JOB_NAME" goes missing (i.e. unset). If I remove the export or > (and this is interesting) set "--export=ALL", then I will have > SLURM_JOB_NAME set properly for the job. > > Is this expected behavior? Obviously I've got the workaround (setting > export to all), but it's a little inelegant IMHO. > > Thanks > > Michael
