We have developed a set of unit tests based on LuaUnit for our clusters' submit
filters.
--Troy
From: slurm-users <[email protected]> On Behalf Of Michael
Robbert
Sent: Thursday, May 6, 2021 1:11 PM
To: Slurm User Community List <[email protected]>
Subject: [slurm-users] Testing Lua job submit plugins
I'm wondering if others in the Slurm community have any tips or best practices
for the development and testing of Lua job submit plugins. Is there anything
that can be done prior to deployment on a production cluster that will help to
ensure the code is going to do what you think it does or at the very least not
prevent any jobs from being submitted? I realize that any configuration change
in slurm.conf could break everything, but I feel like adding Lua code adds
enough complexity that I'm a little more hesitant to just throw it in. Any way
to run some kind of linting or sanity tests on the Lua script? Additionally,
does the script get read in one time at startup or reconfig or can it be
changed on the fly just by editing the file?
Maybe a separate issue, but does anybody have an recipes to build a local test
cluster in Docker that could be used to test this? I was working on one, but
broke my local Docker install and thought I'd send this note out while I was
working on rebuilding it.
Thanks in advance,
Mike Robbert
