On Wed, Mar 12, 2014 at 11:44 AM, Antti Kantee <[email protected]> wrote:
> On 12/03/14 11:04, Justin Cormack wrote:
>> I have set up an hourly rump kernel build against NetBSD head here.
>>
>> http://build.myriabit.eu:8012/waterfall
>>
>> Will add some more hosts. Aim is to be able to spot upstream breakage
>> sooner.
>
> Nice resource, should maybe put a page on the wiki to link the different
> automated build testers; I'm losing track of all of them.

If you point some subdomains of rumpkernel.org at them (CNAMEs to
build.myriabit.eu) I can at least make them more memorable. But will
add to wiki.

> Now, this type of service will probably catch more generic NetBSD
> failures, which from buildrump.sh's perspective are transient, than
> failures for buildrump.sh.  I think that in the past 1.5 years there
> have been around 5 failures that only affected buildrump.sh.  Maybe if
> some build fails 100 times in a row, it should attract attention, as
> it's more likely a buildrump.sh-only failure.
>
> However, this service will be very useful when I'm considering updating
> the NetBSD source timestamp and want to see if everything is fine with
> the current HEAD and if not, whenabouts it broke.
>
> Just to avoid catching any in-flight commits, maybe change the script to
> checkout an explicit timestamp instead of HEAD, e.g.:
> ./checkout.sh cvs nbsrc -D "$(TZ=UTC date +'%Y%m%d %H%M' -d '30 min
> ago')UTC"
> (as a side-effect that also documents how to checkout the tree from when
> failures started)

Will do.

j

------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/13534_NeoTech
_______________________________________________
rumpkernel-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/rumpkernel-users

Reply via email to