zorba-coders team mailing list archive

[Chris Hillery <chillery+launchpad@xxxxxxxxx>]

Other branches have been ok on the RQ machine with a 40-minute timeout. Why
does this branch take so much longer? If it added a great many slow tests
then that's probably ok, but if something is causing everything to go
slower than that's a problem. Maybe ask on zorba-dev if it would be
possible to run the pdash tests on this branch?
On Apr 22, 2012 3:31 PM, "Paul J. Lucas" <paul@xxxxxxxxxxxxx> wrote:

> On Apr 21, 2012, at 10:44 PM, Chris Hillery wrote:
>
> > What seems to be happening with the queue is that the build/test is
> timing out after 40 minutes, which unfortunately doesn't log appropriately.
> I have increased the timeout to 60 minutes and we'll see if it runs. But
> before this gets merged, we should look and see if we can figure out why
> it's taking longer than normal to run with this build.
>
> FYI: On my machine, it took 73 minutes.  The trunk build took 63 minutes.
>
> - Paul
>
>
> --
>
> https://code.launchpad.net/~zorba-coders/zorba/feature-ft_module/+merge/102972
> Your team Zorba Coders is subscribed to branch lp:zorba.
>
> --
> Mailing list: https://launchpad.net/~zorba-coders
> Post to     : zorba-coders@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~zorba-coders
> More help   : https://help.launchpad.net/ListHelp
>

-- 
https://code.launchpad.net/~zorba-coders/zorba/feature-ft_module/+merge/102972
Your team Zorba Coders is subscribed to branch lp:zorba.