The latest SVN commit in r1439145 fixes this.
Cheers,
Chris
On 1/27/13 11:19 AM, "build...@apache.org" wrote:
>The Buildbot has detected a new failure on builder tika-trunk while
>building ASF Buildbot.
>Full details are available at:
> http://ci.apache.org/builders/tika-trunk/builds/1023
>
>Bu
> -Original Message-
> From: Jukka Zitting [mailto:jukka.zitt...@gmail.com]
> Sent: Monday, 21 January 2013 5:50 PM
> To: Tika Development
> Cc: bui...@apache.org
> Subject: Re: buildbot failure in ASF Buildbot on tika-trunk
>
> Hi,
>
> [cc += builds@]
>
Hi,
[cc += builds@]
On Mon, Jan 21, 2013 at 9:16 AM, wrote:
> http://ci.apache.org/builders/tika-trunk/builds/1020
Looks like a buildbot issue: "cp: writing
`/home/buildmaster/master1/public_html/projects/tika/rat-output.xml':
No space left on device"
BR,
Jukka Zitting
Hi,
On Wed, Jul 4, 2012 at 12:13 PM, wrote:
> BUILD FAILED: failed compile
Looks like a Buildbot error. The build works fine for me locally.
BR,
Jukka Zitting
Hi,
On Fri, Jun 29, 2012 at 11:21 PM, wrote:
> The Buildbot has detected a new failure on builder tika-trunk while building
> ASF Buildbot.
Oops, sorry about that. Fixed in revision 1355579.
BR,
Jukka Zitting
Hi,
On Fri, Feb 17, 2012 at 7:26 PM, wrote:
> The Buildbot has detected a new failure on builder tika-trunk
Sorry, my config handling change apparently broke OSGi service
loading. I'll fix that later tonight.
BR,
Jukka Zitting
On Nov 13, 2010, at 7:06am, Jukka Zitting wrote:
Hi,
From: Maxim Valyanskiy [mailto:max...@jet.msk.su]
Hm, build timed out on artifact download stage...
It's probably a problem with the repository.apache.org server that's
recently been running out of memory quite often. The infra team is
Hi,
From: Maxim Valyanskiy [mailto:max...@jet.msk.su]
> Hm, build timed out on artifact download stage...
It's probably a problem with the repository.apache.org server that's recently
been running out of memory quite often. The infra team is aware of the issue.
BR,
Jukka Zitting
Hello!
Hm, build timed out on artifact download stage...
best wishes, Max
13.11.2010 13:50, build...@apache.org пишет:
The Buildbot has detected a new failure of tika-trunk on ASF Buildbot.
Full details are available at:
http://ci.apache.org/builders/tika-trunk/builds/200
Buildbot URL: http
+1...
On 7/14/10 2:27 AM, "Jukka Zitting" wrote:
Hi,
On Tue, Jul 13, 2010 at 3:13 PM, Gav... wrote:
> For future, let me know please if you think it helpful that Tika builds
> continue on Buildbot - with any improvements of extra steps/features
> you want covering, or if you don't see any poi
Hi,
On Wed, Jul 14, 2010 at 3:14 PM, Gav... wrote:
>> We already have a Hudson build [1] that I've been managing. There's
>> nothing wrong having an extra CI build (the more the merrier!), but it
>> needs to be managed by someone on the Tika team to avoid confusion
>> like the one that triggered
> -Original Message-
> From: Jukka Zitting [mailto:jukka.zitt...@gmail.com]
> Sent: Wednesday, 14 July 2010 7:28 PM
> To: bui...@apache.org
> Cc: dev@tika.apache.org
> Subject: Re: buildbot failure in ASF Buildbot on tika-trunk
>
> Hi,
>
> On Tue, Jul 13,
Hi,
On Tue, Jul 13, 2010 at 3:13 PM, Gav... wrote:
> For future, let me know please if you think it helpful that Tika builds
> continue on Buildbot - with any improvements of extra steps/features
> you want covering, or if you don’t see any point and would like it removed.
We already have a Huds
at would be most
useful.
Thanks,
-- Ken
-Original Message-
From: Jukka Zitting [mailto:jukka.zitt...@gmail.com]
Sent: Tuesday, 13 July 2010 7:01 PM
To: bui...@apache.org
Cc: dev@tika.apache.org
Subject: Re: buildbot failure in ASF Buildbot on tika-trunk
Hi,
On Mon, Jul 12, 2010 at 8:35 P
...@gmail.com]
> Sent: Tuesday, 13 July 2010 7:01 PM
> To: bui...@apache.org
> Cc: dev@tika.apache.org
> Subject: Re: buildbot failure in ASF Buildbot on tika-trunk
>
> Hi,
>
> On Mon, Jul 12, 2010 at 8:35 PM, wrote:
> > The Buildbot has detected a new failure of
> -Original Message-
> From: Jukka Zitting [mailto:jukka.zitt...@gmail.com]
> Sent: Tuesday, 13 July 2010 7:01 PM
> To: bui...@apache.org
> Cc: dev@tika.apache.org
> Subject: Re: buildbot failure in ASF Buildbot on tika-trunk
>
> Hi,
>
> On Mon, Ju
Hi,
On Mon, Jul 12, 2010 at 8:35 PM, wrote:
> The Buildbot has detected a new failure of tika-trunk on ASF Buildbot.
> Full details are available at:
> http://ci.apache.org/builders/tika-trunk/builds/49
Gavin, I assume you set up the Tika build on buildbot? Can you change
the build command fro
This looks like another case of the Maven "site" target build
dependency bug:
http://ci.apache.org/builders/tika-trunk/builds/49/steps/compile/logs/stdio
The TikaCLI code is getting compiled before the tika-parsers jar has
been built.
-- Ken
On Jul 12, 2010, at 10:35am, build...@apache.or
Yep, exactly Ken, +1 to the solution proposed.
Cheers,
Chris
On 7/8/10 11:44 AM, "Ken Krugler" wrote:
Hi Chris,
Wait, I think the issue is that the 'site' target triggers the
compilation of the sources, before the jars are built.
Yup, just found a good description - it's a Maven bug:
http:/
Hi Chris,
Wait, I think the issue is that the 'site' target triggers the
compilation of the sources, before the jars are built.
Yup, just found a good description - it's a Maven bug:
http://jira.codehaus.org/browse/MNG-2979
I believe it would work to do "mvn clean install" and then "mvn sit
Hey Ken,
Yep, I think basically if we just do a mvn clean install at the top level of
tika, it will build and install tika-core in order. My guess is that right now
Buildbot is just doing a mvn test without doing the install first. Jukka can
probably shed some more light here...
Cheers,
Chris
Hi Chris,
See here:
http://ci.apache.org/builders/tika-trunk/builds/46/steps/compile/logs/stdio
This has to do with the issue of the tika-core jar which Ken's patch
updated not being used and an older (likely previous nightly)
SNAPSHOT being used. Maybe we should update the builder to do a
See here:
http://ci.apache.org/builders/tika-trunk/builds/46/steps/compile/logs/stdio
This has to do with the issue of the tika-core jar which Ken's patch updated
not being used and an older (likely previous nightly) SNAPSHOT being used.
Maybe we should update the builder to do an mvn install a
23 matches
Mail list logo
