You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@jena.apache.org by Apache Jenkins Server <je...@builds.apache.org> on 2013/09/11 11:57:14 UTC
Build failed in Jenkins: Jena_Development_Test_Windows #202
See <https://builds.apache.org/job/Jena_Development_Test_Windows/202/changes>
Changes:
[andy] Fix script
------------------------------------------
Started by an SCM change
Building remotely on windows1 in workspace <https://builds.apache.org/job/Jena_Development_Test_Windows/ws/>
Cleaning up <https://builds.apache.org/job/Jena_Development_Test_Windows/ws/trunk>
Updating http://svn.apache.org/repos/asf/jena/trunk at revision '2013-09-11T10:52:40.153 +0100'
U jena-tdb\bin\tdbloader2
U apache-jena\bin\tdbloader2
At revision 1521771
Parsing POMs
ERROR: Failed to parse POMs
hudson.util.IOException2: remote file operation failed: <https://builds.apache.org/job/Jena_Development_Test_Windows/ws/trunk> at hudson.remoting.Channel@5dfd6a9b:windows1
at hudson.FilePath.act(FilePath.java:905)
at hudson.FilePath.act(FilePath.java:882)
at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.parsePoms(MavenModuleSetBuild.java:920)
at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:652)
at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:567)
at hudson.model.Run.execute(Run.java:1603)
at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:506)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:246)
Caused by: hudson.remoting.ProxyException: hudson.maven.MavenModuleSetBuild$MavenExecutionException: org.apache.maven.project.ProjectBuildingException: Some problems were encountered while processing the POMs:
[FATAL] Non-resolvable parent POM: Could not find artifact org.apache.jena:jena-parent:pom:7-SNAPSHOT and 'parent.relativePath' points at no local POM @ line 27, column 11
at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:1323)
at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:1058)
at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2423)
at hudson.remoting.UserRequest.perform(UserRequest.java:118)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
at hudson.remoting.Request$2.run(Request.java:326)
at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at hudson.remoting.Engine$1$1.run(Engine.java:63)
at java.lang.Thread.run(Unknown Source)
Caused by: hudson.remoting.ProxyException: org.apache.maven.project.ProjectBuildingException: Some problems were encountered while processing the POMs:
[FATAL] Non-resolvable parent POM: Could not find artifact org.apache.jena:jena-parent:pom:7-SNAPSHOT and 'parent.relativePath' points at no local POM @ line 27, column 11
at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:364)
at hudson.maven.MavenEmbedder.buildProjects(MavenEmbedder.java:361)
at hudson.maven.MavenEmbedder.readProjects(MavenEmbedder.java:331)
at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:1260)
... 12 more
Fwd: Jenkins build is unstable: Jena_Development_Test_Windows #203
Posted by Andy Seaborne <an...@apache.org>.
The windows job hasn't run in quite some while due to several other
things (mostly no server, then it couldn't find the snapshot parent as
it was so far out of step); it now has run.
The full console output is:
https://builds.apache.org/job/Jena_Development_Test_Windows/203/consoleFull
tl;dr: Windows+TDB+mmap needs special handling in testing.
I'm ignoring this for the build (unless someone shouts).
- - - - - - -
It looks to me like the JDBC/TDB tests are trying to delete a mmap
database and reuse the directory. TDB itself does different things on
Windows to *nix. It uses a different directory for every test database
- they are deleted as usual and go away when the JVM exits.
See for example TestDatasetTDBPersist.
Andy
-------- Original Message --------
Subject: Jenkins build is unstable: Jena_Development_Test_Windows #203
Date: Wed, 11 Sep 2013 19:47:31 +0000 (UTC)
From: Apache Jenkins Server <je...@builds.apache.org>
Reply-To: dev@jena.apache.org
To: commits@jena.apache.org
See
<https://builds.apache.org/job/Jena_Development_Test_Windows/203/changes>
Jenkins build is back to stable : Jena_Development_Test_Windows
#209
Posted by Apache Jenkins Server <je...@builds.apache.org>.
See <https://builds.apache.org/job/Jena_Development_Test_Windows/209/changes>
Jenkins build is still unstable: Jena_Development_Test_Windows #208
Posted by Apache Jenkins Server <je...@builds.apache.org>.
See <https://builds.apache.org/job/Jena_Development_Test_Windows/changes>
Jenkins build is still unstable: Jena_Development_Test_Windows #207
Posted by Apache Jenkins Server <je...@builds.apache.org>.
See <https://builds.apache.org/job/Jena_Development_Test_Windows/changes>
Jenkins build is still unstable: Jena_Development_Test_Windows #206
Posted by Apache Jenkins Server <je...@builds.apache.org>.
See <https://builds.apache.org/job/Jena_Development_Test_Windows/changes>
Jenkins build is still unstable: Jena_Development_Test_Windows #205
Posted by Apache Jenkins Server <je...@builds.apache.org>.
See <https://builds.apache.org/job/Jena_Development_Test_Windows/changes>
Jenkins build is still unstable: Jena_Development_Test_Windows #204
Posted by Apache Jenkins Server <je...@builds.apache.org>.
See <https://builds.apache.org/job/Jena_Development_Test_Windows/changes>
Jenkins build is unstable: Jena_Development_Test_Windows #203
Posted by Apache Jenkins Server <je...@builds.apache.org>.
See <https://builds.apache.org/job/Jena_Development_Test_Windows/203/changes>