<div dir="ltr">Woot!</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Jul 9, 2014 at 6:41 PM, Mark Cerqueira <span dir="ltr"><<a href="mailto:mark.cerqueira@gmail.com" target="_blank">mark.cerqueira@gmail.com</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"><span style="font-family:arial,sans-serif;font-size:12.727272033691406px">Hi all,</span><div style="font-family:arial,sans-serif;font-size:12.727272033691406px">
<br></div><div style="font-family:arial,sans-serif;font-size:12.727272033691406px">
In between some intense StarCrafting, Spencer and I set up ChucK to be continuously integrated on Travis CI. This means every commit/change to ChucK ensures ChucK compiles on Mac (10.9.2) and Linux (Ubuntu 12.04), as well as running a bunch of unit tests on both platforms. </div>
<div style="font-family:arial,sans-serif;font-size:12.727272033691406px"><br></div><div style="font-family:arial,sans-serif;font-size:12.727272033691406px"><a href="https://travis-ci.org/ccrma/chuck/builds" target="_blank">https://travis-ci.org/ccrma/chuck/builds</a><br>
</div><div style="font-family:arial,sans-serif;font-size:12.727272033691406px"><br></div><div style="font-family:arial,sans-serif;font-size:12.727272033691406px">This was spurred by the recent 147th shred removal causing a segmentation fault, given we could easily test (and even further stress test) ChucK automatically. Tests are currently in the src/test folder of the ChucK repo on GitHub, including tests like Michael Heuer's 147 spork (and one with over 9000 shreds) removal code in the 04-Stress folder:</div>
<div style="font-family:arial,sans-serif;font-size:12.727272033691406px"><br></div><div style="font-family:arial,sans-serif;font-size:12.727272033691406px"><a href="https://github.com/ccrma/chuck/tree/master/src/test" target="_blank">https://github.com/ccrma/chuck/tree/master/src/test</a><br>
<br></div><div style="font-family:arial,sans-serif;font-size:12.727272033691406px">Want to contribute? Feel free to fork the ChucK repo, add tests, and send a pull request. We're not quite sure how we want to organize the tests yet so put them in whatever folder you want. Once your tests are pulled in, they'll be run every time a new commit is pushed to ChucK.</div>
<div style="font-family:arial,sans-serif;font-size:12.727272033691406px"><br></div><div style="font-family:arial,sans-serif;font-size:12.727272033691406px">We're hoping this will make ChucK more stable as well as decreasing the chance for regressing bugs.</div>
<span class="HOEnZb"><font color="#888888">
<div style="font-family:arial,sans-serif;font-size:12.727272033691406px"><br></div><div style="font-family:arial,sans-serif;font-size:12.727272033691406px">-Mark </div></font></span></div>
<br>_______________________________________________<br>
chuck-dev mailing list<br>
<a href="mailto:chuck-dev@lists.cs.princeton.edu">chuck-dev@lists.cs.princeton.edu</a><br>
<a href="https://lists.cs.princeton.edu/mailman/listinfo/chuck-dev" target="_blank">https://lists.cs.princeton.edu/mailman/listinfo/chuck-dev</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br>Tom Lieber<br><a href="http://AllTom.com/" target="_blank">http://AllTom.com/</a><br><a href="http://infinite-sketchpad.com/" target="_blank">http://infinite-sketchpad.com/</a>
</div>