You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@continuum.apache.org by Steven Vetzal <st...@threewisemen.ca> on 2006/08/14 13:50:48 UTC
False Build Errors
Hi All,
I installed Continuum (v1.0.3) for the first time the other week and
added a bunch of projects to it. The installation was great, although
this is on one of our FreeBSD 64-bit boxes and I had to patch and
compile Tanuki's Wrapper for the platform and graft it into the
Continuum installation.
I have one problem - builds will fail regularly with "Build in Error"
the status icon, but when I go looking for a build error in the build
logs, it only shows me the last successful build.
If I manually trigger another build, it will run successfully and the
status icon will update to show it was successful.
This only seems to happen when I leave it on its own and it does its
hourly checks.
Looking through wrapper.log there are no errors noted.
Anyone seen this before?
Steve
RE: False Build Errors
Posted by Andreas Guther <An...@markettools.com>.
I have noticed that too; I am having Continuum 1.0.3 running on a
Windows system. But I do not see that on a regular basis, rather as an
exception that occurs from time to time.
Andreas
-----Original Message-----
From: Steven Vetzal [mailto:steve@threewisemen.ca]
Sent: Monday, August 14, 2006 4:51 AM
To: Continuum Users
Subject: False Build Errors
Hi All,
I installed Continuum (v1.0.3) for the first time the other week and
added a bunch of projects to it. The installation was great, although
this is on one of our FreeBSD 64-bit boxes and I had to patch and
compile Tanuki's Wrapper for the platform and graft it into the
Continuum installation.
I have one problem - builds will fail regularly with "Build in Error"
the status icon, but when I go looking for a build error in the build
logs, it only shows me the last successful build.
If I manually trigger another build, it will run successfully and the
status icon will update to show it was successful.
This only seems to happen when I leave it on its own and it does its
hourly checks.
Looking through wrapper.log there are no errors noted.
Anyone seen this before?
Steve