<div dir="ltr"><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small">Well, suffice it to say, with the nanocommit model, I feel like I got a lot done today.</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small">See below.</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small"><br></div><div class="gmail_extra"><div class="gmail_quote">On Thu, Nov 13, 2014 at 7:30 PM, Boisvert, Sebastien <span dir="ltr"><<a href="mailto:boisvert@anl.gov" target="_blank">boisvert@anl.gov</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I pulled your branch. Thanks.<br>
<span class=""><br>
> temporarily modify a test<br>
> to fail so I can ensure that the error code propagates back to make, and it was successful. Oddly, make is returning 2 when only 1 is returned by run-unit-tests.sh.<br>
<br>
</span>This is make that is returning 2 when there were errors.<br></blockquote><div><br></div><div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small;display:inline">Yes, of course. I totally had forgotten about the make error semantics. It all makes sense! That's why people should RTFM.</div></div><div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small;display:inline"></div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
>From "man make":<br>
<br>
EXIT STATUS<br>
GNU make exits with a status of zero if all makefiles were successfully parsed and no targets that were built failed. A status of one will be returned if the -q flag was used and make determines<br>
that a target needs to be rebuilt. A status of two will be returned if any errors were encountered.<br></blockquote><div><br></div><div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small;display:inline">Yes!</div></div><div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small;display:inline"></div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">> Will look into this further, but I did confirm that when all tests pass, I get 0 as the result<br>
> of make test.<br>
<br>
</span>Perfect !<br></blockquote><div><br></div><div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small;display:inline">FYI, I have also pushed out a number of nanocommits for you. This includes the scripts to run examples, application tests, and a few more items as Chief .gitignore Officer. We've now got *.log and *.junit.xml on our .gitignore list. I did not break these out into nanocommits, because it's abundantly clear we don't want either ever going into a repository.</div></div><div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small;display:inline"><br></div></div><div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small;display:inline">Well, before I mess something up, i had better call it a night. :-) I'm looking forward to working on the next version of distributed hello. Then I should be well on my way to the systolic array. Things are really starting to make sense.</div></div><div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small;display:inline"><br></div></div><div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small;display:inline">George</div></div></div></div></div>