Exclusive/exclusivity key
Hello @dbeltran and @bdepaula,
Autosubmit Version
v4.1.3
Expid affected(If applicable)
a1ep
Summary
In the ClimateDT workflow we currently have --exclusive
as custom directive. I was trying to change this https://earth.bsc.es/gitlab/digital-twins/de_340-2/workflow/-/issues/428 but I think that:
- The documentation is outdated: In the documentation, it says "EXCLUSIVITY" but it was not working for me, I saw in https://earth.bsc.es/gitlab/es/autosubmit/-/blob/master/autosubmit/platforms/headers/slurm_header.py#L119 that the correct word should be
EXCLUSIVE
(I think!!) - I tried to use
EXCLUSIVE
but it is not working :(
Could you check that everything is correct (both in my experiment/branch and in the code)? Thanks a lot!!
Steps to reproduce
I think that creating an experiment and trying to use EXCLUSIVE
/EXCLUSIVITY
as a key under JOBS
should reproduce what I have.
What is the current bug behavior?
In my report I have: JOBS.DQC.EXCLUSIVE=True
but in the script I get with inspect is not there. I also tried with setting "True" (with the commas).
What is the expected correct behavior?
The --exclusive
flag should be in the slurm script.
Relevant logs and/or screenshots(if applicable)
#!/bin/bash
###############################################################################
# DQC a1ep EXPERIMENT
###############################################################################
#
#SBATCH --qos=gp_debug
#SBATCH -A ehpc01
#
#SBATCH --cpus-per-task=1
#
#SBATCH --nodes=1
#SBATCH -n 1
#
#SBATCH -t 00:30:00
#SBATCH -J a1ep_19900101_fc0_20_DQC
#SBATCH --output=/gpfs/scratch/ehpc01/bsc032376/a1ep/LOG_a1ep/a1ep_19900101_fc0_20_DQC.cmd.out.0
#SBATCH --error=/gpfs/scratch/ehpc01/bsc032376/a1ep/LOG_a1ep/a1ep_19900101_fc0_20_DQC.cmd.err.0
#SBATCH --export=ALL
#SBATCH --hint=nomultithread
#
#
Any other relevant information(if applicable)
()