I'm not sure where I found the windows-2012-3 tag but copied it from some of the output. It looks like we fail for a different error-prone reason in the latest build with a different file issue:
https://builds.apache.org/view/J/view/jclouds/job/jclouds-compat/lastBuild/GUAVA_VERSION=21.0,GUICE_VERSION=3.0,JDK=1.7/console On Tue, Oct 16, 2018 at 08:35:01AM +0200, Ignasi Barrera wrote: > It actually builds on Ubuntu. Look at the first lines of the console output: > > [EnvInject] - Loading node environment variables. > Building remotely on H28 <https://builds.apache.org/computer/H28> > (ubuntu xenial) in workspace > /home/jenkins/jenkins-slave/workspace/jclouds > > > > On Tue, Oct 16, 2018, 07:24 Andrew Gaul <g...@apache.org> wrote: > > > On Mon, Oct 15, 2018 at 06:32:43PM +0200, Ignasi Barrera wrote: > > > We are configuring the new CI environment in the ASF's Jenkins, and > > > there are some unicode-related tests that have started failing: > > > https://builds.apache.org/view/J/view/jclouds/job/jclouds/2/ > > > > > > @gaul (or anyone), you probably are more familiar with those tests > > > than me. Could you have a look? > > > > I tried a few things changing the encoding here: > > > > > > https://support.cloudbees.com/hc/en-us/articles/360004397911-How-to-address-issues-with-unmappable-characters- > > > > I notice that jclouds builds on windows-2012-3; could we change this to > > a Linux variant? This may address the issue and I don't have the > > resources to debug further on Windows. > > > > -- > > Andrew Gaul > > http://gaul.org/ > > -- Andrew Gaul http://gaul.org/
