We're seeing problems on H10 of the form:
Exception in thread "main" java.lang.ClassNotFoundException:
hudson.remoting.Launcher
As far as I can tell, it's only H10.
Andy
Forwarded Message
Subject: Build failed in Jenkins: Jena_Development_Test #2451
Date: Fri, 5 Aug
r.java:410)
Archiving artifacts
Sending e-mails to: notificati...@qpid.apache.org
Finished: FAILURE
On 6 August 2016 at 11:43, Andy Seaborne wrote:
We're seeing problems on H10 of the form:
Exception in thread "main" java.lang.ClassNotFoundException:
hudson.remoting.Launcher
As far
On Tue, Aug 9, 2016 at 8:25 AM, Andy Seaborne wrote:
It looks like podling Taverna is also affected - I found a bunch of jobs
on H0, H4, H8, H9 that have failed recently.
One oddity is that
H0 : failure : Aug 8th
https://builds.apache.org/job/incubator-taverna-commandline-nightly/208/
yet:
H0
Please create a folder for Jena, with rights for all Jena committers.
Thanks
Andy
On 16/07/2020 17:33, Gavin McDonald wrote:
Hi All,
This NOTICE is for everyone on builds.apache.org. We are migrating to a new
Cloudbees based Client Master called https://ci-builds.apache.org. Th
On 18/03/13 16:33, Patrick Hunt wrote:
Thanks Niklas, however it's still failing with the same error, jenkins
reports it's running on "windows1". Any ideas?
https://builds.apache.org/view/S-Z/view/ZooKeeper/job/ZooKeeper-trunk-WinVS2008/771/console
Build started 3/18/2013 8:31:08 AM.
Project
"
On 24/03/13 06:28, Ted Dunning wrote:
I see a continuing pattern of jobs failing on Jenkins. This happens with
Mahout-Quality and Drill-Physical-Plan. Both jobs are totally stable on
other platforms and do not involve non-deterministic tests. In any case,
these failures can occur long before t
Jena builds are getting exit code 143 from maven; the build seems to
going just fine up to that point.
Does any one have any clues/pointers as to how to fix this?
The only consistent point seems to be ubuntu4 but that was working OK 2
days ago at build #653.
The build is given 30 mins - it n
On 23/05/13 19:09, Andy Seaborne wrote:
Jena builds are getting exit code 143 from maven; the build seems to
going just fine up to that point.
Does any one have any clues/pointers as to how to fix this?
The only consistent point seems to be ubuntu4 but that was working OK 2
days ago at build
to run Maven, the above
code will do nothing on Java 6 and the bugs stays.
Uwe
-
Uwe Schindler
uschind...@apache.org
Apache Lucene PMC Member / Committer
Bremen, Germany
http://lucene.apache.org/
-----Original Message-
From: Andy Seaborne [mailto:a...@apache.org]
Sent: Sunday, Jun
So have Jena builds.
Andy
On 12/07/13 19:48, Billie Rinaldi wrote:
Accumulo builds are gone as well.
On Jul 12, 2013 1:35 PM, "Giridharan Kesavan"
wrote:
Restarted jenkins master.
-Giri
On Fri, Jul 12, 2013 at 5:11 AM, Olivier Lamy wrote:
ooops!
no idea on what the hell!!
Someo
e suppose to be deleted and I deleted them :-).
There should be 3 showing - a nightly SNAPSHOT deployment, a development
triggered build and a Windows build.
There are no jobs showing.
https://builds.apache.org/view/H-L/view/Jena/
Andy
-Giri
On Fri, Jul 12, 2013 at 12:21 PM, And
On 22/11/13 08:05, Gavin McDonald wrote:
Hi All,
So I tried to get a Windows 2012 Server r2 up and running but our VMWare
(4.x) didn't like it much so for now we
have a 2nd Windows Server 2008 r2 up and running.
Labels are now 'Windows' to choose either slave, windows1 for the older
slave and w
On 22/11/13 11:05, Gavin McDonald wrote:
ah, all there , I just need to re-create the symlinks for 'latest-x.x'
will let you know when done.
Try now please, symlinks for latest* added.
Trying:
Maven 3(latest) ==>
ERROR: Maven Home f:\jenkins\tools\maven\latest3 doesn’t exist
but using ma
Our jobs tied to Ubuntu slaves do not seem to be getting triggered by
svn polling. Slaves in label: 6
Example job:
https://builds.apache.org/user/andy/my-views/view/Jena/job/Jena_Development_Test
has SVN polling log:
https://builds.apache.org/user/andy/my-views/view/Jena/job/Jena_Developmen
with the error a few minutes after I'd
changed the maven setting; it has now started working.
Andy
Andy Seaborne hat am 9. Januar 2014 um 14:33 geschrieben:
Our jobs tied to Ubuntu slaves do not seem to be getting triggered by
svn polling. Slaves in label: 6
Example j
On 19/01/14 19:31, Hervé BOUTEMY wrote:
Hi,
FYI, I created https://issues.apache.org/jira/browse/INFRA-7211
In case somebody with karma reads this list more than Jira...
Regards,
Hervé
See
http://mail-archives.apache.org/mod_mbox/www-builds/201401.mbox/%3C1378381618.267108.1389275204401.o
We have some bit rot in our Jenkin windows job:
https://builds.apache.org/job/Jena_Development_Test_Windows/
I can't even wipe the workspace at the moment.
windows2:
java.io.FileNotFoundException:
C:\Windows\TEMP\junit2341214733363083535\folder with space\file with
space.ttl.new (There is no
Andy Seaborne created BUILDS-33:
---
Summary: Jenakin to GIT fetch timeouts
Key: BUILDS-33
URL: https://issues.apache.org/jira/browse/BUILDS-33
Project: Infra Build Platform
Issue Type: Bug
[
https://issues.apache.org/jira/browse/BUILDS-33?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne updated BUILDS-33:
Summary: Jenkins to GIT fetch timeouts (Jena) (was: Jenakin to GIT fetch
timeouts)
> Jenkins
[
https://issues.apache.org/jira/browse/BUILDS-33?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14229750#comment-14229750
]
Andy Seaborne commented on BUILDS-33:
-
Thanks for the update. There are no errors
[
https://issues.apache.org/jira/browse/BUILDS-33?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne closed BUILDS-33.
---
Reran the jobs and didn't see any problems.
> Jenkins to GIT fetch timeou
Andy Seaborne created BUILDS-42:
---
Summary: Jenkins to GIT fetch errors (Jena)
Key: BUILDS-42
URL: https://issues.apache.org/jira/browse/BUILDS-42
Project: Infra Build Platform
Issue Type: Bug
[
https://issues.apache.org/jira/browse/BUILDS-42?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne resolved BUILDS-42.
-
Resolution: Done
Wiping the projects workspaces seems to have made the builds work again. (maybe
Andy Seaborne created BUILDS-61:
---
Summary: H10: Bad file in maven repo
Key: BUILDS-61
URL: https://issues.apache.org/jira/browse/BUILDS-61
Project: Infra Build Platform
Issue Type: Bug
[
https://issues.apache.org/jira/browse/BUILDS-65?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14376224#comment-14376224
]
Andy Seaborne commented on BUILDS-65:
-
Apologies.
The Jena job is using way too
[
https://issues.apache.org/jira/browse/BUILDS-92?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne updated BUILDS-92:
Description:
This is occuring on multiple projects (e.g. any23, Jena) and multiple machines
(ubuntu
Andy Seaborne created BUILDS-92:
---
Summary: Jenkins not sending email
Key: BUILDS-92
URL: https://issues.apache.org/jira/browse/BUILDS-92
Project: Infra Build Platform
Issue Type: Bug
27 matches
Mail list logo