<div dir="ltr"><div><div><div><div><div><div>Hi,<br><br></div>It is committed. NEMSLegacy revision is 84036 and nems revision is 84035. <br><br></div>Notes:<br></div>1. New external added to produtil<br></div>2. REGRESSION_TEST and REGRESSION_TEST_baselines have new content to support the new regression test implementation. The test results are not changed.<br><br></div><div>I'm syncing the regression tests over to Gyre/Surge now. It may take several hours, but it should finish before the next production switch.<br></div><div><br></div>Sincerely,<br></div>Sam Trahan<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Nov 2, 2016 at 3:40 AM, Samuel Trahan - NOAA Affiliate <span dir="ltr"><<a href="mailto:samuel.trahan@noaa.gov" target="_blank">samuel.trahan@noaa.gov</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div>Hello all,<br><br></div>I'm going to commit the new regression tests between 1-2 PM Eastern time November 2 (today). The regression test data will remain in emc.nemspara.<br><br>The emc.nemspara issues on Theia are corrected. Apparently the problem was in a new script the Theia admins wrote for /etc/sudoers file maintenance. I will separately contact the code managers to make sure they can all access emc.nemspara.<br><br></div>Sincerely,<br></div>Sam Trahan<br></div><div class="gmail_extra"><br><div class="gmail_quote"><span class="">On Mon, Oct 31, 2016 at 3:24 PM, Samuel Trahan - NOAA Affiliate <span dir="ltr"><<a href="mailto:samuel.trahan@noaa.gov" target="_blank">samuel.trahan@noaa.gov</a>></span> wrote:<br></span><div><div class="h5"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div>Hello all,<br><br></div>The new regression test scripts will be committed Tuesday evening, but the exact time is unknown due to Theia account issues. The emc.nemspara account sudo access is broken on Theia, so I have no way to update the regression test data. If all else fails, we'll switch ownership of regression test data back to Ratko or myself and update the scripts accordingly. If you have an urgent commit, please let me know so I can switch ownership sooner.<br><br></div><div>The branch urls are below. Note the addition of a new "produtil" external at the NEMSLegacy level. The python produtil library is used to automate some of the new regression tests; it is a lot like the prod_util module on WCOSS operations. It is not used for any other purpose, so the old regression tests (and everything else) will still work if you lack the new external.<br><br></div><div>I will commit to the NEMSLegacy trunk, nems trunk and produtil trunk at the same time, probably Tuesday evening. The exact timing is contingent on when the emc.nemspara access is restored, or when I give up waiting for RDHPCS admins to fix that problem.<br></div><div><br></div><div>NEMSLegacy branch:</div><div><a href="https://svnemc.ncep.noaa.gov/projects/nems/apps/NEMSLegacy/branches/regtests-update" target="_blank">https://svnemc.ncep.noaa.gov/p<wbr>rojects/nems/apps/NEMSLegacy/b<wbr>ranches/regtests-update</a><br><br></div><div>NEMS branch:<br><a href="https://svnemc.ncep.noaa.gov/projects/nems/branches/regtests-update" target="_blank">https://svnemc.ncep.noaa.gov/p<wbr>rojects/nems/branches/regtests<wbr>-update</a><br></div><div><br></div><div>produtil branch:<br><a href="https://svnemc.ncep.noaa.gov/projects/nceplibs/produtil/branches/regtests" target="_blank">https://svnemc.ncep.noaa.gov/p<wbr>rojects/nceplibs/produtil/bran<wbr>ches/regtests</a><br></div><div><br></div>Sincerely,<br></div>Sam Trahan<br></div>
</blockquote></div></div></div><br></div>
</blockquote></div><br></div>