Continuum works differently from the old bash script in a couple of
ways. First, it only executes builds when svn changes have happened.
So if there are no changes, there will be no "nightly build" for a
component. It also looks for changes and executes builds hourly, so
there can be multiple bui
Hi Will
I haven't yet got a chance to look at this in detail.. but your patch
seems to be only for compress? and not for the VFS provider? If so its
not clear to me how can one use it for VFS
thanks
asankha
Will Pugh wrote:
I wrote some zip writing code for compress that can modify the actua
On 8/24/07, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
> Henri Yandell wrote:
> > Everything seems to build (that's in CI), except:
> >
> > * Compress - Dennis discovered that this is an EOL issue.
> > * VFS - has a failing test, both in and out of CI.
> > * FileUpload - failing tests in CI, works
Henri Yandell wrote:
Everything seems to build (that's in CI), except:
* Compress - Dennis discovered that this is an EOL issue.
* VFS - has a failing test, both in and out of CI.
* FileUpload - failing tests in CI, works out of CI.
* Configuration - failing tests (55!) in CI, I get 1 failure ou
Instead of having nightly builds, couldn't we maybe set it up so that
these projects only build when necessary (svn changes, checked
nightly)? The build number could be synced with the SVN repository's
revision number, maybe? That way, we know how to recreate the build
if need be.
On 8/24/07, [E
I wrote some zip writing code for compress that can modify the actual
zip files. I submitted it and then fell off the face of the earth. In
July, I came back an fixed up some of the concerns, but I think the
pause ended up losing some of the interest in this.
http://issues.apache.org/jira/br
Online report :
http://vmbuild.apache.org/continuum/buildResult.action?buildId=2383&projectId=161
Build statistics:
State: Failed
Previous State: Failed
Started at: Fri 24 Aug 2007 08:30:28 -0700
Finished at: Fri 24 Aug 2007 08:31:16 -0700
Total time: 48s
Build Trigger: Schedule
Build Num
Looking at the test reports, all test failures seem to be caused by
dependencies to java.awt classes, which cannot be resolved. (For
instance, DataConfiguration supports some data types like
java.awt.Color, and the test class tries to check this).
Is there anything we can do about this?
Olive
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project commons-jelly-tags-jsl-test has an issue affecting its community
integration.
Th
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project commons-id has an issue affecting its community integration.
This issue affects 1
Online report :
http://vmbuild.apache.org/continuum/buildResult.action?buildId=2359&projectId=161
Build statistics:
State: Failed
Previous State: Failed
Started at: Fri 24 Aug 2007 03:42:49 -0700
Finished at: Fri 24 Aug 2007 03:43:39 -0700
Total time: 50s
Build Trigger: Schedule
Build Num
Hi,
> I would be interested to see write support for files such as Jar, Tar
> and Zip etc in VFS. If you already have some code that works, thats great
ok, i didn't finish all the code necessary, but i remember there are
only smaller chunks left to write.
> I am a Jakarta HttpCore committer as w
Hi Chris
I would be interested to see write support for files such as Jar, Tar
and Zip etc in VFS. If you already have some code that works, thats great
Since i am not a comitter i found it very difficult to contribute and my
interest dissappeard too.
I am a Jakarta HttpCore committer as wel
There is usually a web interface, but we discovered late that it
wasn't being displayed in the Continuum 1.1-beta-2 release. There
should be another release in the next couple of weeks that addresses
it directly.
In the mean time, you can browse to the working directory to see the
surefire reports
* JCI - failing test both in and out of CI.
The drools guys found a bug and I added a testcase that reproduces
the problem.
Need to work this out with the janino team.
cheers
--
Torsten
-
To unsubscribe, e-mail: [EMAIL PR
Henri Yandell wrote:
> Everything seems to build (that's in CI), except:
>
> * Configuration - failing tests (55!) in CI, I get 1 failure out of CI.
Is there a way of having a look at the surefire reports? I would like to
dig into this.
The major part of the failing tests might be due to a missi
Online report :
http://vmbuild.apache.org/continuum/buildResult.action?buildId=2333&projectId=21
Build statistics:
State: Failed
Previous State: Ok
Started at: Fri 24 Aug 2007 00:25:19 -0700
Finished at: Fri 24 Aug 2007 00:27:42 -0700
Total time: 2m 22s
Build Trigger: Forced
Build Number:
17 matches
Mail list logo