On 5/13/18 10:07 AM, Bryan Pendleton wrote:
Hi Rick,

On both the environments I have available (Windows 10 / JDK 9.0.4 and
Fedora / JDK 9.0.1) all those tests passed without issue.

Eyeballing the details of the Jenkins run in
https://builds.apache.org/blue/organizations/jenkins/Derby-trunk-suites.All/detail/Derby-trunk-suites.All/169/tests/
it certainly seems to me like the issue involves international characters
in permissions files. All of the failed tests complain about access denied
errors for java.io.FilePermission on file paths which contain
filename components in international character sets.

Maybe that's a clue as to what's different about the Jenkins slave?
Thanks. That is a good clue. I will ponder this.

Also, and I think unrelated, did you happen to see the errors in
https://builds.apache.org/job/Derby-trunk/2554/display/redirect?page=changes

Those errors are in the 'publishedapi' target, and the message is:

install_packagelists:
     [mkdir] Created dir:
<https://builds.apache.org/job/Derby-trunk/ws/trunk/packageListLoc-se-8>
     [mkdir] Created dir:
<https://builds.apache.org/job/Derby-trunk/ws/trunk/packageListLoc-j2ee-7>
       [get] Getting: http://docs.oracle.com/javase/8/docs/api/package-list
       [get] To:
<https://builds.apache.org/job/Derby-trunk/ws/trunk/packageListLoc-se-8/package-list>
       [get] http://docs.oracle.com/javase/8/docs/api/package-list
permanently moved to
https://docs.oracle.com/javase/8/docs/api/package-list

BUILD FAILED
<https://builds.apache.org/job/Derby-trunk/ws/trunk/build.xml>:999:
The following error occurred while executing this line:
<https://builds.apache.org/job/Derby-trunk/ws/trunk/build.xml>:1027:
Redirection detected from http to https. Protocol switch unsafe, not
allowed.

Looking at the value of 'javasedoc.url' in our build.xml file:

    <property name="javasedoc.url"
value="http://docs.oracle.com/javase/8/docs/api"/>

two things occur to me:

1) Should we change it from java 8 to java 9?
Yes, absolutely!

2) Can we simply change the url to specify https rather than http? If
that works,
then we probably have to do that for j2eedoc.url also?
I can reach the following url, which looks like the right one for our javadoc to access:

https://docs.oracle.com/javase/9/docs/api

Most of the other javadoc urls look stale to me. We haven't brushed the dust off this part of the build for a long time. The j2ee url should be

https://docs.oracle.com/javaee/7/api/

I'm not sure what values to choose for javasedoc.local and j2eedoc.local. Maybe change the first to

   <property name="javasedoc.local" value="packageListLoc-se-9"/>

Thanks!
-Rick

Thanks again for all the help getting these cleaned up, I will be happier if
we are getting clean runs from our Jenkins system.

bryan


Reply via email to