You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@continuum.apache.org by Anoop kumar V <an...@gmail.com> on 2007/01/26 15:41:38 UTC
Build has been in enqueued status for almost 18 hours
Here is the log:
250 2.0.0 l0PLI3TW028009 Message accepted for delivery
QUIT
2007-01-25 16:18:06,173 [Thread-2] INFO MsnClient - Connection. Waiting for
the response....
2007-01-25 16:18:07,793 [MSN Channel(NS)] INFO MsnClient - Connected.
2007-01-25 16:21:41,725 [SocketListener0-6] INFO Continuum
2007-01-25 16:21:41,725 [SocketListener0-6] INFO Continuum - Enqueuing 'CapOne
AutoProv (TEST)' (Build definition id=10).
2007-01-25 16:28:19,556 [SocketListener0-6] ERROR VelocityComponent - RHS of
#set statement is null. Context will not be modified.
screens/ProjectBuild.vm [line 103, column 3]
2007-01-26 09:36:14,422 [SocketListener0-11] INFO Action:login - Trying to
log in 'admin'.
username: admin
I think the previous build failed in the notifications step. had setup some
msn IM notifications and for some reason it could not connect to the MSN
accounts. ( Isee in the logs that it connected eventually) But since then it
has been in the enqueued stage.
What can I do to tell it to move along... ( I have now removed the msn
notifications, but still no go)
--
Thanks and best regards,
Anoop
Re: Build has been in enqueued status for almost 18 hours
Posted by Anoop kumar V <an...@gmail.com>.
funnily, all the other builds were also blocked.. they were just enqueued. I
did not want to build all, so I deleted the first project which was causing
the enqueued build and recreated it again. But as soon as recreated 9and
before I hit build), it started checking out code into a new folder. Is that
expected?
Well - when I hit build, even the new project was enqueued - so no builds
were going through.
Finally I restarted continuum and now all builds are running just fine.
I think it would be good to have an option of de-queuing a build that has
been enqueued.
Thanks,
Anoop
On 1/26/07, Emmanuel Venisse <em...@venisse.net> wrote:
>
> You can try to restart your continuum. if the state doesn't change aftert
> the restart, click the 'build all' button.
>
> I don't think it's a pb with the msn notifier.
>
> Emmanuel
>
> Anoop kumar V a écrit :
> > Here is the log:
> >
> > 250 2.0.0 l0PLI3TW028009 Message accepted for delivery
> > QUIT
> > 2007-01-25 16:18:06,173 [Thread-2] INFO MsnClient - Connection. Waiting
> > for
> > the response....
> > 2007-01-25 16:18:07,793 [MSN Channel(NS)] INFO MsnClient - Connected.
> > 2007-01-25 16:21:41,725 [SocketListener0-6] INFO Continuum
> > 2007-01-25 16:21:41,725 [SocketListener0-6] INFO Continuum - Enqueuing
> > 'CapOne
> > AutoProv (TEST)' (Build definition id=10).
> > 2007-01-25 16:28:19,556 [SocketListener0-6] ERROR VelocityComponent -
> > RHS of
> > #set statement is null. Context will not be modified.
> > screens/ProjectBuild.vm [line 103, column 3]
> > 2007-01-26 09:36:14,422 [SocketListener0-11] INFO Action:login -
> > Trying to
> > log in 'admin'.
> > username: admin
> >
> > I think the previous build failed in the notifications step. had setup
> > some
> > msn IM notifications and for some reason it could not connect to the MSN
> > accounts. ( Isee in the logs that it connected eventually) But since
> > then it
> > has been in the enqueued stage.
> >
> > What can I do to tell it to move along... ( I have now removed the msn
> > notifications, but still no go)
> >
> >
>
>
--
Thanks and best regards,
Anoop
Re: Build has been in enqueued status for almost 18 hours
Posted by Emmanuel Venisse <em...@venisse.net>.
You can try to restart your continuum. if the state doesn't change aftert the restart, click the 'build all' button.
I don't think it's a pb with the msn notifier.
Emmanuel
Anoop kumar V a écrit :
> Here is the log:
>
> 250 2.0.0 l0PLI3TW028009 Message accepted for delivery
> QUIT
> 2007-01-25 16:18:06,173 [Thread-2] INFO MsnClient - Connection. Waiting
> for
> the response....
> 2007-01-25 16:18:07,793 [MSN Channel(NS)] INFO MsnClient - Connected.
> 2007-01-25 16:21:41,725 [SocketListener0-6] INFO Continuum
> 2007-01-25 16:21:41,725 [SocketListener0-6] INFO Continuum - Enqueuing
> 'CapOne
> AutoProv (TEST)' (Build definition id=10).
> 2007-01-25 16:28:19,556 [SocketListener0-6] ERROR VelocityComponent -
> RHS of
> #set statement is null. Context will not be modified.
> screens/ProjectBuild.vm [line 103, column 3]
> 2007-01-26 09:36:14,422 [SocketListener0-11] INFO Action:login -
> Trying to
> log in 'admin'.
> username: admin
>
> I think the previous build failed in the notifications step. had setup
> some
> msn IM notifications and for some reason it could not connect to the MSN
> accounts. ( Isee in the logs that it connected eventually) But since
> then it
> has been in the enqueued stage.
>
> What can I do to tell it to move along... ( I have now removed the msn
> notifications, but still no go)
>
>