Build failed in Jenkins: JClouds » jclouds #105

2024-03-02 Thread Apache Jenkins Server 
See 


Changes:

[Andrew Gaul] JCLOUDS-1626: Close stream in MultiBlobInputStream


--
Started by an SCM change
Running as SYSTEM
[EnvInject] - Loading node environment variables.
Building remotely on builds29 (ubuntu) in workspace 

The recommended git tool is: NONE
No credentials specified
Cloning the remote Git repository
Cloning repository https://gitbox.apache.org/repos/asf/jclouds.git
 > git init  # 
 > timeout=10
Fetching upstream changes from https://gitbox.apache.org/repos/asf/jclouds.git
 > git --version # timeout=10
 > git --version # 'git version 2.34.1'
 > git fetch --tags --force --progress -- 
 > https://gitbox.apache.org/repos/asf/jclouds.git 
 > +refs/heads/*:refs/remotes/origin/* # timeout=10
 > git config remote.origin.url https://gitbox.apache.org/repos/asf/jclouds.git 
 > # timeout=10
 > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # 
 > timeout=10
Avoid second fetch
 > git rev-parse refs/remotes/origin/master^{commit} # timeout=10
Checking out Revision 4c7fb2c8b9f36207cd0b04f6266521412e6678f3 
(refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 4c7fb2c8b9f36207cd0b04f6266521412e6678f3 # timeout=10
Commit message: "JCLOUDS-1626: Close stream in MultiBlobInputStream"
 > git rev-list --no-walk 4f3955799bb8e419556c9590dd60faed5d3122dd # timeout=10
[EnvInject] - Executing scripts and injecting environment variables after the 
SCM step.
[EnvInject] - Injecting as environment variables the properties content 
LC_ALL=en_US.UTF-8
LANG=en_US.UTF-8

[EnvInject] - Variables injected successfully.
Parsing POMs
Modules changed, recalculating dependency graph
Established TCP socket on 44415
maven35-agent.jar already up to date
maven35-interceptor.jar already up to date
maven3-interceptor-commons.jar already up to date
[jclouds] $ /home/jenkins/tools/java/latest1.8/bin/java -cp 
/home/jenkins/maven35-agent.jar:/home/jenkins/tools/maven/apache-maven-3.5.4/boot/plexus-classworlds-2.5.2.jar:/home/jenkins/tools/maven/apache-maven-3.5.4/conf/logging
 jenkins.maven3.agent.Maven35Main /home/jenkins/tools/maven/apache-maven-3.5.4 
/home/jenkins/agent.jar /home/jenkins/maven35-interceptor.jar 
/home/jenkins/maven3-interceptor-commons.jar 44415
Exception in thread "main" java.lang.UnsupportedClassVersionError: 
hudson/remoting/Launcher has been compiled by a more recent version of the Java 
Runtime (class file version 55.0), this version of the Java Runtime only 
recognizes class file versions up to 52.0
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:756)
at 
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:473)
at java.net.URLClassLoader.access$100(URLClassLoader.java:74)
at java.net.URLClassLoader$1.run(URLClassLoader.java:369)
at java.net.URLClassLoader$1.run(URLClassLoader.java:363)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:362)
at 
org.codehaus.plexus.classworlds.realm.ClassRealm.loadClassFromSelf(ClassRealm.java:401)
at 
org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:42)
at 
org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadClass(ClassRealm.java:271)
at 
org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:247)
at 
org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:239)
at jenkins.maven3.agent.Maven35Main.main(Maven35Main.java:136)
at jenkins.maven3.agent.Maven35Main.main(Maven35Main.java:66)
ERROR: Failed to parse POMs
java.io.EOFException: unexpected stream termination
at hudson.remoting.ChannelBuilder.negotiate(ChannelBuilder.java:459)
at hudson.remoting.ChannelBuilder.build(ChannelBuilder.java:404)
at hudson.slaves.Channels.forProcess(Channels.java:121)
at 
hudson.maven.AbstractMavenProcessFactory.newProcess(AbstractMavenProcessFactory.java:298)
at hudson.maven.ProcessCache.get(ProcessCache.java:237)
at 
hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:802)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:526)
at hudson.model.Run.execute(Run.java:1841)
at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:543)
at hudson.model.ResourceController.execute(ResourceController.java:101)
at hudson.model.Executor.run(Executor.java:442)

[jira] [Resolved] (JCLOUDS-1626) `FileInputStream` leak when using `filesystem` provider and performing a multipart upload

2024-03-02 Thread Andrew Gaul (Jira) 


 [ 
https://issues.apache.org/jira/browse/JCLOUDS-1626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Gaul resolved JCLOUDS-1626.
--
  Assignee: Andrew Gaul
Resolution: Fixed

This is a problem with S3Proxy, not jclouds and probably addressed by 
https://github.com/gaul/s3proxy/commit/ec12ae0fe502aaae858ee60c256376c604b07093.
  Please provide a proper test case in the future.

> `FileInputStream` leak when using `filesystem` provider and performing a 
> multipart upload
> -
>
> Key: JCLOUDS-1626
> URL: https://issues.apache.org/jira/browse/JCLOUDS-1626
> Project: jclouds
>  Issue Type: Bug
>  Components: jclouds-blobstore
>Reporter: Ji Xinchi
>Assignee: Andrew Gaul
>Priority: Critical
>  Labels: filesystem
>
> I'm using gaul/s3proxy built on the latest jclouds. The provider 
> configuration is "filesystem", and basedir configuration is a directory where 
> a NFS is mounted.
>  
> When I performed a multipart upload, I found that files such as 
> ".nfs10bf0005" remained in the directory after uploading. 
> Each file corresponded to one part and the files could not be deleted. The 
> error "Device Busy" was reported. These files will disappear automatically 
> after restarting s3proxy.
>  
> I found this PR, and tried to restore following snippet and it worked. But 
> this is just a temporary fix.
> {code:java}
>  InputStream is = blob.getPayload().openStream();
>  if (is instanceof FileInputStream) {
> // except for FileInputStream since large MPU can open too many 
> fds
> is.close();
> payload = blob.getPayload();
>  } else {
> blob.resetPayload(/*release=*/ false);
> payload = new InputStreamPayload(is);
>  } {code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Commented] (JCLOUDS-1626) `FileInputStream` leak when using `filesystem` provider and performing a multipart upload

2024-03-02 Thread ASF subversion and git services (Jira) 


[ 
https://issues.apache.org/jira/browse/JCLOUDS-1626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17822884#comment-17822884
 ] 

ASF subversion and git services commented on JCLOUDS-1626:
--

Commit 4c7fb2c8b9f36207cd0b04f6266521412e6678f3 in jclouds's branch 
refs/heads/master from Andrew Gaul
[ https://gitbox.apache.org/repos/asf?p=jclouds.git;h=4c7fb2c8b9 ]

JCLOUDS-1626: Close stream in MultiBlobInputStream

Otherwise the inner FileInputStream will leak if the caller only reads
part of the stream before closing the outer MultiBlobInputStream.


> `FileInputStream` leak when using `filesystem` provider and performing a 
> multipart upload
> -
>
> Key: JCLOUDS-1626
> URL: https://issues.apache.org/jira/browse/JCLOUDS-1626
> Project: jclouds
>  Issue Type: Bug
>  Components: jclouds-blobstore
>Reporter: Ji Xinchi
>Priority: Critical
>  Labels: filesystem
>
> I'm using gaul/s3proxy built on the latest jclouds. The provider 
> configuration is "filesystem", and basedir configuration is a directory where 
> a NFS is mounted.
>  
> When I performed a multipart upload, I found that files such as 
> ".nfs10bf0005" remained in the directory after uploading. 
> Each file corresponded to one part and the files could not be deleted. The 
> error "Device Busy" was reported. These files will disappear automatically 
> after restarting s3proxy.
>  
> I found this PR, and tried to restore following snippet and it worked. But 
> this is just a temporary fix.
> {code:java}
>  InputStream is = blob.getPayload().openStream();
>  if (is instanceof FileInputStream) {
> // except for FileInputStream since large MPU can open too many 
> fds
> is.close();
> payload = blob.getPayload();
>  } else {
> blob.resetPayload(/*release=*/ false);
> payload = new InputStreamPayload(is);
>  } {code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Commented] (JCLOUDS-1626) `FileInputStream` leak when using `filesystem` provider and performing a multipart upload

2024-03-02 Thread Andrew Gaul (Jira) 


[ 
https://issues.apache.org/jira/browse/JCLOUDS-1626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17822883#comment-17822883
 ] 

Andrew Gaul commented on JCLOUDS-1626:
--

Apparently this is referencing b7f28f1e6a2632fce579360c7900b6dc548ff25f.

> `FileInputStream` leak when using `filesystem` provider and performing a 
> multipart upload
> -
>
> Key: JCLOUDS-1626
> URL: https://issues.apache.org/jira/browse/JCLOUDS-1626
> Project: jclouds
>  Issue Type: Bug
>  Components: jclouds-blobstore
>Reporter: Ji Xinchi
>Priority: Critical
>  Labels: filesystem
>
> I'm using gaul/s3proxy built on the latest jclouds. The provider 
> configuration is "filesystem", and basedir configuration is a directory where 
> a NFS is mounted.
>  
> When I performed a multipart upload, I found that files such as 
> ".nfs10bf0005" remained in the directory after uploading. 
> Each file corresponded to one part and the files could not be deleted. The 
> error "Device Busy" was reported. These files will disappear automatically 
> after restarting s3proxy.
>  
> I found this PR, and tried to restore following snippet and it worked. But 
> this is just a temporary fix.
> {code:java}
>  InputStream is = blob.getPayload().openStream();
>  if (is instanceof FileInputStream) {
> // except for FileInputStream since large MPU can open too many 
> fds
> is.close();
> payload = blob.getPayload();
>  } else {
> blob.resetPayload(/*release=*/ false);
> payload = new InputStreamPayload(is);
>  } {code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Build failed in Jenkins: JClouds » jclouds-with-credentials » jclouds-compute-delete-all #67

2024-03-02 Thread Apache Jenkins Server 
See 


Changes:


--
Started by upstream project 
"JClouds/jclouds-with-credentials/jclouds-packet-live-tests" build number 185
originally caused by:
 Started by timer
Running as SYSTEM
No JDK named ‘JDK 1.8.0_144 (unlimited security)’ found
[EnvInject] - Loading node environment variables.
Building remotely on builds32 (ubuntu) in workspace 

No JDK named ‘JDK 1.8.0_144 (unlimited security)’ found
The recommended git tool is: NONE
No credentials specified
No JDK named ‘JDK 1.8.0_144 (unlimited security)’ found
Cloning the remote Git repository
Cloning repository https://gitbox.apache.org/repos/asf/karaf-jclouds-cli.git
 > git init 
 > 
 >  # timeout=10
Fetching upstream changes from 
https://gitbox.apache.org/repos/asf/karaf-jclouds-cli.git
 > git --version # timeout=10
 > git --version # 'git version 2.34.1'
 > git fetch --tags --force --progress -- 
 > https://gitbox.apache.org/repos/asf/karaf-jclouds-cli.git 
 > +refs/heads/*:refs/remotes/origin/* # timeout=10
 > git config remote.origin.url 
 > https://gitbox.apache.org/repos/asf/karaf-jclouds-cli.git # timeout=10
 > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # 
 > timeout=10
Avoid second fetch
 > git rev-parse refs/remotes/origin/master^{commit} # timeout=10
No JDK named ‘JDK 1.8.0_144 (unlimited security)’ found
Checking out Revision fdc566154e25a0d44f8dab5a65ee01da1e78b9be 
(refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f fdc566154e25a0d44f8dab5a65ee01da1e78b9be # timeout=10
Commit message: "fix typo in project.version"
 > git rev-list --no-walk fdc566154e25a0d44f8dab5a65ee01da1e78b9be # timeout=10
[EnvInject] - Mask passwords that will be passed as build parameters.
No JDK named ‘JDK 1.8.0_144 (unlimited security)’ found
[jclouds-compute-delete-all] $ mvn clean package
FATAL: command execution failed
java.io.IOException: error=2, No such file or directory
at java.base/java.lang.ProcessImpl.forkAndExec(Native Method)
at java.base/java.lang.ProcessImpl.(ProcessImpl.java:340)
at java.base/java.lang.ProcessImpl.start(ProcessImpl.java:271)
at java.base/java.lang.ProcessBuilder.start(ProcessBuilder.java:1107)
Also:   hudson.remoting.Channel$CallSiteStackTrace: Remote call to builds32
at 
hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1787)
at 
hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:356)
at hudson.remoting.Channel.call(Channel.java:1003)
at hudson.Launcher$RemoteLauncher.launch(Launcher.java:1121)
at hudson.Launcher$ProcStarter.start(Launcher.java:506)
at hudson.Launcher$ProcStarter.join(Launcher.java:517)
at hudson.tasks.Maven.perform(Maven.java:369)
at 
hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:818)
at hudson.model.Build$BuildExecution.build(Build.java:199)
at hudson.model.Build$BuildExecution.doRun(Build.java:164)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:526)
at hudson.model.Run.execute(Run.java:1841)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:44)
at 
hudson.model.ResourceController.execute(ResourceController.java:101)
at hudson.model.Executor.run(Executor.java:442)
Caused: java.io.IOException: Cannot run program "mvn" (in directory 
":
 error=2, No such file or directory
at java.base/java.lang.ProcessBuilder.start(ProcessBuilder.java:1128)
at java.base/java.lang.ProcessBuilder.start(ProcessBuilder.java:1071)
at hudson.Proc$LocalProc.(Proc.java:252)
at hudson.Proc$LocalProc.(Proc.java:221)
at hudson.Launcher$LocalLauncher.launch(Launcher.java:994)
at hudson.Launcher$ProcStarter.start(Launcher.java:506)
at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1395)
at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1337)
at hudson.remoting.UserRequest.perform(UserRequest.java:211)
at hudson.remoting.UserRequest.perform(UserRequest.java:54)
at hudson.remoting.Request$2.run(Request.java:377)
at 
hudson.remoting.InterceptingExecutorService.lambda$wrap$0(InterceptingExecutorService.java:78)
at

Build failed in Jenkins: JClouds » jclouds-with-credentials » jclouds-packet-live-tests #185

2024-03-02 Thread Apache Jenkins Server 
See 


Changes:

[Andrew Gaul] JCLOUDS-1629: Upgrade to Guice 7.0.0

[Andrew Gaul] JCLOUDS-1628: Remove Netty driver


--
Started by timer
Running as SYSTEM
[EnvInject] - Loading node environment variables.
Building remotely on builds29 (ubuntu) in workspace 

The recommended git tool is: NONE
No credentials specified
 > git rev-parse --resolve-git-dir 
 > 
 >  # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url https://gitbox.apache.org/repos/asf/jclouds.git 
 > # timeout=10
Fetching upstream changes from https://gitbox.apache.org/repos/asf/jclouds.git
 > git --version # timeout=10
 > git --version # 'git version 2.34.1'
 > git fetch --tags --force --progress -- 
 > https://gitbox.apache.org/repos/asf/jclouds.git 
 > +refs/heads/*:refs/remotes/origin/* # timeout=10
 > git rev-parse refs/remotes/origin/master^{commit} # timeout=10
Checking out Revision 4f3955799bb8e419556c9590dd60faed5d3122dd 
(refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 4f3955799bb8e419556c9590dd60faed5d3122dd # timeout=10
Commit message: "JCLOUDS-1628: Remove Netty driver"
 > git rev-list --no-walk b5e4e1d0fd466dffcbb0fb7921e52732145cc732 # timeout=10
[EnvInject] - Mask passwords that will be passed as build parameters.
Parsing POMs
Modules changed, recalculating dependency graph
Established TCP socket on 42533
maven35-agent.jar already up to date
maven35-interceptor.jar already up to date
maven3-interceptor-commons.jar already up to date
[jclouds-packet-live-tests] $ /home/jenkins/tools/java/latest1.8/bin/java -cp 
/home/jenkins/maven35-agent.jar:/home/jenkins/tools/maven/latest/boot/plexus-classworlds-2.7.0.jar:/home/jenkins/tools/maven/latest/conf/logging
 jenkins.maven3.agent.Maven35Main /home/jenkins/tools/maven/latest 
/home/jenkins/agent.jar /home/jenkins/maven35-interceptor.jar 
/home/jenkins/maven3-interceptor-commons.jar 42533
Exception in thread "main" java.lang.UnsupportedClassVersionError: 
hudson/remoting/Launcher has been compiled by a more recent version of the Java 
Runtime (class file version 55.0), this version of the Java Runtime only 
recognizes class file versions up to 52.0
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:756)
at 
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:473)
at java.net.URLClassLoader.access$100(URLClassLoader.java:74)
at java.net.URLClassLoader$1.run(URLClassLoader.java:369)
at java.net.URLClassLoader$1.run(URLClassLoader.java:363)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:362)
at 
org.codehaus.plexus.classworlds.realm.ClassRealm.findClassInternal(ClassRealm.java:313)
at 
org.codehaus.plexus.classworlds.realm.ClassRealm.loadClassFromSelf(ClassRealm.java:432)
at 
org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:42)
at 
org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadClass(ClassRealm.java:271)
at 
org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:247)
at 
org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:239)
at jenkins.maven3.agent.Maven35Main.main(Maven35Main.java:136)
at jenkins.maven3.agent.Maven35Main.main(Maven35Main.java:66)
ERROR: Failed to parse POMs
java.io.EOFException: unexpected stream termination
at hudson.remoting.ChannelBuilder.negotiate(ChannelBuilder.java:459)
at hudson.remoting.ChannelBuilder.build(ChannelBuilder.java:404)
at hudson.slaves.Channels.forProcess(Channels.java:121)
at 
hudson.maven.AbstractMavenProcessFactory.newProcess(AbstractMavenProcessFactory.java:298)
at hudson.maven.ProcessCache.get(ProcessCache.java:237)
at 
hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:802)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:526)
at hudson.model.Run.execute(Run.java:1841)
at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:543)
at hudson.model.ResourceController.execute(ResourceController.java:101)
at hudson.model.Executor.run(Executor.java:442)