[OpenAFS-devel] Re: 'make check' buildslave updates..

Thu, 6 Sep 2012 00:34:44 -0400

--e89a8ff1c4eabf630b04c9010276
Content-Type: text/plain; charset=ISO-8859-1

That would be step 6, after any issues have been resolved after the push to
gerrit.

Nathan.
On Sep 5, 2012 8:24 PM, "Jason Edgecombe" <jason@rampaginggeek.com> wrote:

> On 09/05/2012 03:37 PM, Derrick Brashear wrote:
>
>> On Thu, Jun 14, 2012 at 1:20 PM, Troy Benjegerdes <hozer@hozed.org>
>> wrote:
>>
>>> On Mon, Apr 16, 2012 at 07:28:23PM -0400, Derrick Brashear wrote:
>>>
>>>> 1) make the tests be built as part of "make all"; push to gerrit. it
>>>> may fail. if so,
>>>>
>>> now builds (current iteration of 7225)
>>
>> so i guess after the predecessor patchsets are merged, we can move on to
>> step 4.
>>
>>  2) attempt make the tests actually build on all platforms; rebase that
>>>> change before the one described in 1, and push both to gerrit.
>>>> 3) iterate on 2 until things build everywhere
>>>> 4) a simple way to then work on getting the tests working everywhere
>>>> without breaking every slave: submit a change which makes "make check"
>>>> happen as part
>>>> of "make all"; mark it not to be merged, but buildbot will happily
>>>> explode wherever a buildslave would be screwed.
>>>> 5) fix it or decide we don't care or each platform, iterating over 4.
>>>> 6) when we know which platforms are done, turn it on for those
>>>> platforms.
>>>>
>>> I wanted to follow up and see how we were doing on this list..
>>> Is there anything I could be doing that might help?
>>>
>>
>>
>>  Should I add the "make check" step as a build step on some, but not all,
> of the buildslaves? That would not require an "all or nothing" approach. If
> you want make check on some of the buildslaves. Just let me know which ones.
>
> Jason
>
> Jason
> ______________________________**_________________
> OpenAFS-devel mailing list
> OpenAFS-devel@openafs.org
> https://lists.openafs.org/**mailman/listinfo/openafs-devel<https://lists.openafs.org/mailman/listinfo/openafs-devel>
>

--e89a8ff1c4eabf630b04c9010276
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

That would be step 6, after any issues have been resolved after the push=
 to gerrit.
Nathan.
<div class=3D"gmail_quote">On Sep 5, 2012 8:24 PM, &quot;Jason Edgecombe&qu=
ot; &lt;<a href=3D"mailto:jason@rampaginggeek.com">jason@rampaginggeek.com<=
/a>&gt; wrote: <blockquote class=3D"gmail_quote" st=
yle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On 09/05/2012 03:37 PM, Derrick Brashear wrote: 
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
On Thu, Jun 14, 2012 at 1:20 PM, Troy Benjegerdes &lt;<a href=3D"mailto:hoz=
er@hozed.org" target=3D"_blank">hozer@hozed.org</a>&gt; wrote: 
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
On Mon, Apr 16, 2012 at 07:28:23PM -0400, Derrick Brashear wrote: 
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
1) make the tests be built as part of &quot;make all&quot;; push to gerrit.=
 it 
may fail. if so, 
</blockquote></blockquote>
now builds (current iteration of 7225) 
 
so i guess after the predecessor patchsets are merged, we can move on to st=
ep 4. 
 
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><blockquote class=3D"gmail_quote" style=3D"m=
argin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
2) attempt make the tests actually build on all platforms; rebase that 
change before the one described in 1, and push both to gerrit. 
3) iterate on 2 until things build everywhere 
4) a simple way to then work on getting the tests working everywhere 
without breaking every slave: submit a change which makes &quot;make check&=
quot; 
happen as part 
of &quot;make all&quot;; mark it not to be merged, but buildbot will happil=
y 
explode wherever a buildslave would be screwed. 
5) fix it or decide we don&#39;t care or each platform, iterating over 4.<b=
r>
6) when we know which platforms are done, turn it on for those platforms.<b=
r>
</blockquote>
I wanted to follow up and see how we were doing on this list.. 
Is there anything I could be doing that might help? 
</blockquote>
 
 
</blockquote>
Should I add the &quot;make check&quot; step as a build step on some, but n=
ot all, of the buildslaves? That would not require an &quot;all or nothing&=
quot; approach. If you want make check on some of the buildslaves. Just let=
 me know which ones.

<br>
Jason<br>
<br>
Jason<br>
______________________________<u></u>_________________<br>
OpenAFS-devel mailing list<br>
<a href=3D"mailto:OpenAFS-devel@openafs.org" target=3D"_blank">OpenAFS-deve=
l@openafs.org</a><br>
<a href=3D"https://lists.openafs.org/mailman/listinfo/openafs-devel" target=
=3D"_blank">https://lists.openafs.org/<u></u>mailman/listinfo/openafs-devel=
</a><br>
</blockquote></div>

--e89a8ff1c4eabf630b04c9010276--