<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body dir="auto">
I’ve used the structure at <a href="https://gist.github.com/mikerenfro/92d70562f9bb3f721ad1b221a1356de5">https://gist.github.com/mikerenfro/92d70562f9bb3f721ad1b221a1356de5</a> to handle basic test/production branching. I can isolate the new behavior down to
just a specific set of UIDs that way.
<div><br>
</div>
<div>Factoring out code into separate functions helps, too.</div>
<div><br>
</div>
<div>I’ve seen others go so far as to put the functions into separate files, but I haven’t needed that yet.<br>
<div dir="ltr"><br>
<blockquote type="cite">On May 6, 2021, at 12:11 PM, Michael Robbert <mrobbert@mines.edu> wrote:<br>
<br>
</blockquote>
</div>
<blockquote type="cite">
<div dir="ltr">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:12.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:12.0pt;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style>
<p align="center" style="text-align:center;
background:white;margin:0px"><b><span style="font-size:12.0pt;color:red;background:white;
font-family:"Calibri",sans-serif">External Email Warning</span></b></p>
<p align="center" style="text-align:center;
background:white;margin:0px 12pt"><b><span style="font-size:12.0pt;color:red;font-family:"Calibri",sans-serif">This email originated from outside the university. Please use caution when opening attachments, clicking
links, or responding to requests.</span></b><span style="font-size:12.0pt"></span></p>
<hr>
<div>
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt">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? <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">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. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Thanks in advance,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Mike Robbert<o:p></o:p></span></p>
</div>
</div>
</div>
</blockquote>
</div>
</body>
</html>