The Test Bot seems to be having issues

[Thomas Mullaly]

Hi all,

First off, I'm not sure who should be contacted about this, but, it appears
that the test bot has got itself stuck while trying to run tests on a patch
submitted last night. The job in question is here [1], it's been over 12
hours since any progress has been made on it and no other submissions have
run since then. Also, the Windows 98SE has been "reverting" this whole time,
so I'm not sure if this is the culprit or not.

I also hate to admit that the job in question is from one of my patches I
sent in last night (although I'm pretty sure it doesn't have anything to do
with the quality of the code in the patch ;-) ).

Anyways, I'm hoping that somebody in charge of the test bot might be able to
fix the traffic jam it's causing.

[1] https://testbot.winehq.org/JobDetails.pl?Key=4570
https://testbot.winehq.org/JobDetails.pl?Key=4570

[GOUJON Alexandre]

On 08/19/2010 07:56 PM, Thomas Mullaly wrote:
> First off, I'm not sure who should be contacted about this

It's Grep Geldorp but wine-devel is a good place too.
> , but, it appears that the test bot has got itself stuck while trying 
> to run tests on a patch submitted last night. The job in question is 
> here [1], it's been over 12 hours since any progress has been made on 
> it and no other submissions have run since then. Also, the Windows 
> 98SE has been "reverting" this whole time, so I'm not sure if this is 
> the culprit or not.

There are some <div> and </div> in your patch.
Anyway, the bot applied your patch successfully and began to run some of 
your tests.

Now, the only thing to do is waiting...

[Thomas Mullaly]

On Fri, Aug 20, 2010 at 4:44 AM, GOUJON Alexandre wrote:
> It's Grep Geldorp but wine-devel is a good place too.

Thanks, hopefully he notices the thread.
> There are some <div> and </div> in your patch.
> Anyway, the bot applied your patch successfully and began to run some of
> your tests.

Hmm... All my patches (coming through wine-patches) seem to end up with
those <div> tags in them, but, they've never caused problems.
> Now, the only thing to do is waiting...

At this point I would be surprised if the Test bot started randomly working
without any assistance. The job has been in the "running" state for 24+
hours already, without any progress being made.