Nour,
This is mine. I think its running tests that it shouldn't. I'll look
into it.
Rob
On 28/11/10 15:32, Mohammad Nour El-Din wrote:
Hey all
Please see the latest build status [1]. Increasing the timeout to
60 mins solved the timeout problem, but we still have test failures
[2], I think we need to sort these ones out as well.
[1] - http://hudson.apache.org/hudson/job/Isis-trunk-windows/7/
[2] -
http://hudson.apache.org/hudson/job/Isis-trunk-windows/org.apache.isis.alternatives.objectstore$nosql/7/testReport/
On Sun, Nov 28, 2010 at 4:10 PM, Mohammad Nour El-Din<[email protected]> wrote:
Hey all...
Dan has pinged me on IRC about sorting out Isis Hudson build cause
last build [1] has failed because of time out. I've configured the
timeout threshold to 30 minutes, so I have increased it to 60 minutes.
Dan has proposed a nicer idea that is to split the build tasks to
build separate modules of the system and hence we control the time
taken by each build job more appropriately. I will go with the 60
minutes configuration for the whole project build for now to make sure
that build itself has no problem, when we make sure I will go with the
separate modules build way.
[1] - http://hudson.apache.org/hudson/job/Isis-trunk-windows/6/
--
Thanks
- Mohammad Nour
Author of (WebSphere Application Server Community Edition 2.0 User Guide)
http://www.redbooks.ibm.com/abstracts/sg247585.html
- LinkedIn: http://www.linkedin.com/in/mnour
- Blog: http://tadabborat.blogspot.com
----
"Life is like riding a bicycle. To keep your balance you must keep moving"
- Albert Einstein
"Writing clean code is what you must do in order to call yourself a
professional. There is no reasonable excuse for doing anything less
than your best."
- Clean Code: A Handbook of Agile Software Craftsmanship
"Stay hungry, stay foolish."
- Steve Jobs
