The internet connection the master is currently on has been somewhat
unstable over the last week causing connection issues. The buildmaster will
be moving to a new box on a better connection over the weekend to help fix
these issues. You will also see the newer slaves at that time.

Travis

On Sat, Jun 16, 2012 at 3:07 AM, Hannu Nyman <hannu.ny...@iki.fi> wrote:

> There has not been successful buildbot snapshots for a week for any
> platform. The buildbot status screens are full of exceptions.
> Alternatively, some of the builds have now been on the make for 37 hours,
> without the displayed status progressing even into the kernel compilation
> status.
> http://tksite.gotdns.org:8010/**grid <http://tksite.gotdns.org:8010/grid>
> http://tksite.gotdns.org:8010/**one_line_per_build<http://tksite.gotdns.org:8010/one_line_per_build>
>
> To me it looks like either the buildbot master has got crazy or all the
> buildslaves have started to experience problems at the same time.
>
> Last 20 finished builds:
> Time     Revision     Result     Builder     Build #     Info
> Jun 14 22:55     32381     retry     iop32x     #30     Build successful
> exception slave lost
> Jun 14 22:55     32381     retry     au1000     #29     Build successful
> exception slave lost
> Jun 14 22:55     32381     retry     ar71xx     #29     Build successful
> exception slave lost
> Jun 14 22:55     32381     exception     avr32     #35     Exception
> shell_4 shell_15 compile_12
> Jun 14 17:09     32376     retry     avr32     #34     Build successful
> exception slave lost
> Jun 14 17:09     32376     exception     x86     #34     Exception shell_4
> shell_15 compile_12
> Jun 14 17:09     32376     exception     sibyte     #34 Exception shell_4
> shell_15 compile_12
> Jun 14 17:09     32376     exception     ar7     #33     Exception shell_4
> shell_15 compile_12
> Jun 13 22:56     32353     retry     avr32     #33     Build successful
> exception slave lost
> Jun 13 22:56     32353     retry     sibyte     #33     Build successful
> exception slave lost
> Jun 13 22:56     32353     retry     ar7     #32     Build successful
> exception slave lost
> Jun 13 22:56     32353     retry     x86     #33     Build successful
> exception slave lost
> Jun 14 05:13     32353     retry     kirkwood     #30     Build successful
> exception slave lost
> Jun 14 05:13     32353     retry     ixp4xx     #31     Build successful
> exception slave lost
> Jun 14 05:13     32353     retry     xburst     #30     Build successful
> exception slave lost
> Jun 14 05:12     32353     retry     s3c24xx     #42     Build successful
> exception slave lost
> Jun 14 04:36     32353     exception     uml     #36     Exception download
> Jun 14 04:35     32353     exception     pxcab     #37     Exception
> download
> Jun 14 04:35     32353     exception     ramips     #37 Exception download
> Jun 14 04:34     32353     retry     s3c24xx     #41     Build successful
> exception slave lost
>
>
> Another buildbot-related question: there have been some messages on the
> list saying that new buildslaves would be available if needed. But I think
> I haven't seen any new slaves being put into use, and only alicia,
> buildslave1 and buildslave2 seem to be doing any work. Have those messages
> went unnoticed? Or were the offered slaves unsuitable?
>
>
> ______________________________**_________________
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.**org <openwrt-devel@lists.openwrt.org>
> https://lists.openwrt.org/**mailman/listinfo/openwrt-devel<https://lists.openwrt.org/mailman/listinfo/openwrt-devel>
>
_______________________________________________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Reply via email to