Hi Matt and all,<br><br>This is great! I am interested in getting involved and am willing to be a user or administrator, whatever makes the most sense.<br><br>I am going to try this week to start some writing tests as well.<br>
<br>Britton<br><br><div class="gmail_quote">On Sun, Oct 14, 2012 at 5:33 PM, Matthew Turk <span dir="ltr"><<a href="mailto:matthewturk@gmail.com" target="_blank">matthewturk@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I forgot to point at the URL for the Shining Panda instance:<br>
<br>
<a href="https://jenkins.shiningpanda-ci.com/yt-project/" target="_blank">https://jenkins.shiningpanda-ci.com/yt-project/</a><br>
<br>
New repos we pull from and test will show up here.<br>
<div class="HOEnZb"><div class="h5"><br>
On Sun, Oct 14, 2012 at 11:41 AM, Matthew Turk <<a href="mailto:matthewturk@gmail.com">matthewturk@gmail.com</a>> wrote:<br>
> Hi Nathan et al,<br>
><br>
> We just got approved for a FLOSS license on Shining Panda. As it<br>
> currently stands, we can't mount EBS volumes, so answer testing will<br>
> not be a part of this initiative as of right now. Kacper's suggested<br>
> we explore other options for answer testing, and I think he's right --<br>
> particularly because we may end up using a lot of memory and putting<br>
> strain on an individual node, and that's probably bad karma. So I<br>
> think we should keep the two somewhat separately tested for now, and<br>
> continue creating unit tests that test either randomly created<br>
> in-memory data or isolated functionality.<br>
><br>
> I can add users and administrators to the SP account:<br>
><br>
> <a href="https://www.shiningpanda-ci.com/docs/dashboard/multiusers.html" target="_blank">https://www.shiningpanda-ci.com/docs/dashboard/multiusers.html</a><br>
><br>
> We also can identify different repos that get pulled from to test. I<br>
> think we definitely want to test the main yt repository and the main<br>
> yt-3.0 repository (once it has tests finalized.) We can also add a<br>
> few "semi-trusted" repositories -- for instance, Sam does a lot of<br>
> development in his fork, so he may want to have it added to the<br>
> buildbots. I do a lot, so I may also want mine added.<br>
><br>
> If you have a "user" role you can make it test any time you want.<br>
><br>
> If you have an administrator role you can do the same but also add new<br>
> repos to test.<br>
><br>
> Would anyone like to be added as a "user"? I think this would also<br>
> need to coincide with having your personal repository added as a<br>
> testing location. For administrator, I think we should restrict to<br>
> people who have been really involved in the pull request and code<br>
> mentoring process.<br>
><br>
> Kacper and I are going to hash out some answer testing stuff in IRC<br>
> before coming back to the list with any ideas. But clearly we need to<br>
> ensure we cover both answer testing AND unit testing in the<br>
> infrastructure we develop.<br>
><br>
> -Matt<br>
><br>
> On Fri, Oct 12, 2012 at 3:28 PM, Nathan Goldbaum <<a href="mailto:nathan12343@gmail.com">nathan12343@gmail.com</a>> wrote:<br>
>> $144/year is well worth it and it's probably good karma to support them since they have to pay for the infrastructure.<br>
>><br>
>> +1 (although it's not my money ;)<br>
>><br>
>> On Oct 12, 2012, at 3:25 PM, Matthew Turk wrote:<br>
>><br>
>>> [snip]<br>
>>><br>
>>>> I've emailed Shining Panda about this, but if they don't<br>
>>>> have the ability to provide us with a FLOSS license, I think we can<br>
>>>> identify some funding to do this.<br>
>>><br>
>>> [snip]<br>
>>><br>
>>> Okay, we're laughably far back in their queue. I'm inclined to think<br>
>>> that if we get a couple people who look at Shining Panda, think it<br>
>>> looks good and so on, that we just upgrade the plan to be paid for so<br>
>>> that we don't have to wait and we can fix this problem now instead of<br>
>>> in some distant date. What do y'all think?<br>
>>><br>
>>> <a href="http://shiningpanda-ci.com" target="_blank">http://shiningpanda-ci.com</a><br>
>>><br>
>>> -Matt<br>
>>> _______________________________________________<br>
>>> yt-dev mailing list<br>
>>> <a href="mailto:yt-dev@lists.spacepope.org">yt-dev@lists.spacepope.org</a><br>
>>> <a href="http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a><br>
>><br>
>> _______________________________________________<br>
>> yt-dev mailing list<br>
>> <a href="mailto:yt-dev@lists.spacepope.org">yt-dev@lists.spacepope.org</a><br>
>> <a href="http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a><br>
_______________________________________________<br>
yt-dev mailing list<br>
<a href="mailto:yt-dev@lists.spacepope.org">yt-dev@lists.spacepope.org</a><br>
<a href="http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a><br>
</div></div></blockquote></div><br>