Re: [CRITICAL] KIO Test "threadtest" can enter into infinite loop

2015-11-10 Thread Albert Astals Cid
El Tuesday 10 November 2015, a les 19:57:50, Ben Cooksley va escriure: > On Mon, Nov 9, 2015 at 8:30 PM, David Faure wrote: > > On Monday 09 November 2015 19:36:09 Ben Cooksley wrote: > >> On Mon, Nov 9, 2015 at 10:26 AM, Albert Astals Cid wrote: > >> > El Saturday

Re: [CRITICAL] KIO Test "threadtest" can enter into infinite loop

2015-11-10 Thread Albert Astals Cid
El Monday 09 November 2015, a les 08:30:14, David Faure va escriure: > On Monday 09 November 2015 19:36:09 Ben Cooksley wrote: > > On Mon, Nov 9, 2015 at 10:26 AM, Albert Astals Cid wrote: > > > El Saturday 07 November 2015, a les 10:36:18, David Faure va escriure: > > >> On

Re: [CRITICAL] KIO Test "threadtest" can enter into infinite loop

2015-11-09 Thread Ben Cooksley
On Mon, Nov 9, 2015 at 8:30 PM, David Faure wrote: > On Monday 09 November 2015 19:36:09 Ben Cooksley wrote: >> On Mon, Nov 9, 2015 at 10:26 AM, Albert Astals Cid wrote: >> > El Saturday 07 November 2015, a les 10:36:18, David Faure va escriure: >> >> On Saturday 07

Re: [CRITICAL] KIO Test "threadtest" can enter into infinite loop

2015-11-08 Thread Albert Astals Cid
El Saturday 07 November 2015, a les 10:36:18, David Faure va escriure: > On Saturday 07 November 2015 11:17:31 Ben Cooksley wrote: > > Hi all, > > > > It appears the test running with the binary name of "threadtest" in > > kio has a grave bug which can lead to it entering into an infinite > >

Re: [CRITICAL] KIO Test "threadtest" can enter into infinite loop

2015-11-08 Thread Nicolás Alvarez
2015-11-07 7:23 GMT-03:00 David Faure : > On Saturday 07 November 2015 10:36:18 David Faure wrote: >> On Saturday 07 November 2015 11:17:31 Ben Cooksley wrote: >> > Hi all, >> > >> > It appears the test running with the binary name of "threadtest" in >> > kio has a grave bug which

Re: [CRITICAL] KIO Test "threadtest" can enter into infinite loop

2015-11-08 Thread Ben Cooksley
On Mon, Nov 9, 2015 at 10:26 AM, Albert Astals Cid wrote: > El Saturday 07 November 2015, a les 10:36:18, David Faure va escriure: >> On Saturday 07 November 2015 11:17:31 Ben Cooksley wrote: >> > Hi all, >> > >> > It appears the test running with the binary name of "threadtest" in

Re: [CRITICAL] KIO Test "threadtest" can enter into infinite loop

2015-11-08 Thread David Faure
On Monday 09 November 2015 19:36:09 Ben Cooksley wrote: > On Mon, Nov 9, 2015 at 10:26 AM, Albert Astals Cid wrote: > > El Saturday 07 November 2015, a les 10:36:18, David Faure va escriure: > >> On Saturday 07 November 2015 11:17:31 Ben Cooksley wrote: > >> > Hi all, > >> > > >> >

Re: [CRITICAL] KIO Test "threadtest" can enter into infinite loop

2015-11-07 Thread David Faure
On Saturday 07 November 2015 11:17:31 Ben Cooksley wrote: > Hi all, > > It appears the test running with the binary name of "threadtest" in > kio has a grave bug which can lead to it entering into an infinite > loop. > > This was consuming virtually the entire resources of one builder with > old

Re: [CRITICAL] KIO Test "threadtest" can enter into infinite loop

2015-11-07 Thread Ben Cooksley
On Sat, Nov 7, 2015 at 11:23 PM, David Faure wrote: > On Saturday 07 November 2015 10:36:18 David Faure wrote: >> On Saturday 07 November 2015 11:17:31 Ben Cooksley wrote: >> > Hi all, >> > >> > It appears the test running with the binary name of "threadtest" in >> > kio has a

Re: [CRITICAL] KIO Test "threadtest" can enter into infinite loop

2015-11-07 Thread David Faure
On Saturday 07 November 2015 10:36:18 David Faure wrote: > On Saturday 07 November 2015 11:17:31 Ben Cooksley wrote: > > Hi all, > > > > It appears the test running with the binary name of "threadtest" in > > kio has a grave bug which can lead to it entering into an infinite > > loop. > > > >

[CRITICAL] KIO Test "threadtest" can enter into infinite loop

2015-11-06 Thread Ben Cooksley
Hi all, It appears the test running with the binary name of "threadtest" in kio has a grave bug which can lead to it entering into an infinite loop. This was consuming virtually the entire resources of one builder with old hung processes, and the whole core of another builder - drastically