Closed dawson6 closed 1 year ago
OK, the 'cpuaffinity' or really any test case can be used to show this issue.
Generally we do not want users runnin 'ats' on the login node, as ats will run jobs and needs to talk to the lsf scheduler.
That is if one takes one of the stanard tests and runs this command on a login node of rzansel.
ats test.ats
It will quit with the message:
ATS DISABLED ON LOGIN NODE OF ANSEL. PLEASE RUN IN AN ALLOCATION.
In contrast if one runs
atslite1 test.ats
it will run as atslite1 will allocate the backend node and run ats there.
HOWEVER, there are use cases some projects have had where they want to force ats to run on the login node. This may be a scenario where ats is running 'non mpi' scripts of some sort and needs to run on the login node.
This definitely should not be the default, but if a user gives an option this would be allowable and that check should be bypassed.
BTW that check is in the file lsf_asq.py, and is easy to fine if one graps for thae above line
Testing this may be tricky, as one needs a test which does not actually use MPI, so a modification of a test which could just be a script that says' hello would work
Closing this issue based on @MishaZakharchanka work.
provide user option to bypass this check