[GitHub] [commons-vfs] garydgregory commented on issue #62: Don’t fail on openjdk-ea builds

2019-05-13 Thread GitBox
garydgregory commented on issue #62: Don’t fail on openjdk-ea builds
URL: https://github.com/apache/commons-vfs/pull/62#issuecomment-491847907
 
 
   Nothing to do IMO, all builds are green on 
https://travis-ci.org/apache/commons-vfs


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] [commons-vfs] garydgregory commented on issue #62: Don’t fail on openjdk-ea builds

2019-04-30 Thread GitBox
garydgregory commented on issue #62: Don’t fail on openjdk-ea builds
URL: https://github.com/apache/commons-vfs/pull/62#issuecomment-487944561
 
 
   I'd like to understand why the PR build passes:
   https://travis-ci.org/apache/commons-vfs/builds/526143774
   AND that build actually ran.
   
   While the master build failed, _not even having started the build_:
   https://travis-ci.org/apache/commons-vfs/jobs/526040009
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] [commons-vfs] garydgregory commented on issue #62: Don’t fail on openjdk-ea builds

2019-04-30 Thread GitBox
garydgregory commented on issue #62: Don’t fail on openjdk-ea builds
URL: https://github.com/apache/commons-vfs/pull/62#issuecomment-487937038
 
 
   Hi @abashev:
   
   I am kinda -1 on openjdk-ea as allowing to fail since we know it always 
fails. What I was trying to say, unsuccessfully ;-) is either:
   - Let's not even put openjdk-ea in the list of jdks if we then say it is 
allowed to fail, since it fails always
   - Make openjdk-ea work, are least work enough that the build starts.
   
   Thoughts?
   
   Gary


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] [commons-vfs] garydgregory commented on issue #62: Don’t fail on openjdk-ea builds

2019-04-29 Thread GitBox
garydgregory commented on issue #62: Don’t fail on openjdk-ea builds
URL: https://github.com/apache/commons-vfs/pull/62#issuecomment-487703396
 
 
   I just don't understand why we have other builds in Commons that can use the 
OpenJDK EA without any issue. In this case, we can't we even start to use it. 
So there must be some configuration thing happening that is allowing some of 
our Travis builds to work like https://travis-ci.org/apache/commons-text


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services


[GitHub] [commons-vfs] garydgregory commented on issue #62: Don’t fail on openjdk-ea builds

2019-04-29 Thread GitBox
garydgregory commented on issue #62: Don’t fail on openjdk-ea builds
URL: https://github.com/apache/commons-vfs/pull/62#issuecomment-487680818
 
 
   The problems seems like a Travis issue:
   ```
   Installing openjdk-ea
   $ export JAVA_HOME=~/openjdk-ea
   $ export PATH="$JAVA_HOME/bin:$PATH"
   $ ~/bin/install-jdk.sh --target "/home/travis/openjdk-ea" --workspace 
"/home/travis/.cache/install-jdk" --feature "ea" --license "GPL" --cacerts
   install-jdk.sh 2019-04-18
   Couldn't determine a download url for 13-GPL on linux-x64
   The command "~/bin/install-jdk.sh --target "/home/travis/openjdk-ea" 
--workspace "/home/travis/.cache/install-jdk" --feature "ea" --license "GPL" 
--cacerts" failed and exited with 1 during .
   Your build has been stopped.
   ```
   Maybe we have to specify a specific OS setup like 'trusty' or some other 
version?


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services