Community
Participate
Working Groups
In the N20160327-2000 the "releng test" says javadoc errors and/or warnings in: platform.doc.isv.javadoc.txt jdt.doc.isv.javadoc.txt pde.doc.user.javadoc.txt See the javadoc logs linked from the test results page for details http://download.eclipse.org/eclipse/downloads/drops4/N20160327-2000/compilelogs/jdt.doc.isv.javadoc.txt http://download.eclipse.org/eclipse/downloads/drops4/N20160327-2000/compilelogs/pde.doc.user.javadoc.txt http://download.eclipse.org/eclipse/downloads/drops4/N20160327-2000/compilelogs/platform.doc.isv.javadoc.txt
At first I assumed true "doc" error, but looking at the error messages, they are all of the form javadoc: warning - Error fetching URL: https://docs.oracle.com/javase/8/docs/api/ javadoc: warning - Error fetching URL: https://docs.oracle.com/javase/8/docs/jre/api/plugin/dom/ javadoc: warning - Error fetching URL: https://osgi.org/javadoc/r6/core/ javadoc: warning - Error fetching URL: https://osgi.org/javadoc/r5/cmpn/ = = = = = = And, in another section of the build, there was also an indication that "proxy settings" are not correct, so I think this is a "releng" problem. = = = = = = If interested in details, this is probably related to bug 487044 where I have started running the "N-builds" from the "Releng HIPP" instance. (At least have not moved I-builds yet, so they should not have this problem ... but suspect I can correct today.)
The HIPP instances appear to have all the following variables set to maximize changes that one of them is appropriate. ANT_OPTS=-Djava.io.tmpdir=/tmp/genie.releng -Dhttp.proxyHost=proxy.eclipse.org -Dhttp.proxyPort=9898 -Dhttps.proxyHost=proxy.eclipse.org -Dhttps.proxyPort=9898 -Dhttp.nonProxyHosts="172.30.206.*" -Dhttps.nonProxyHosts="172.30.206.*" -Dftp.proxyHost=proxy.eclipse.org -Dftp.proxyPort=9898 -Dftp.nonProxyHosts="172.30.206.*" http_proxy=http://proxy.eclipse.org:9898 ftp_proxy=http://proxy.eclipse.org:9898 JVM_OPTS=-Djava.io.tmpdir=/tmp/genie.releng -Dhttp.proxyHost=proxy.eclipse.org -Dhttp.proxyPort=9898 -Dhttps.proxyHost=proxy.eclipse.org -Dhttps.proxyPort=9898 -Dhttp.nonProxyHosts="172.30.206.*" -Dhttps.nonProxyHosts="172.30.206.*" -Dftp.proxyHost=proxy.eclipse.org -Dftp.proxyPort=9898 -Dftp.nonProxyHosts="172.30.206.*" JAVA_ARGS=-Djava.io.tmpdir=/tmp/genie.releng -Dhttp.proxyHost=proxy.eclipse.org -Dhttp.proxyPort=9898 -Dhttps.proxyHost=proxy.eclipse.org -Dhttps.proxyPort=9898 -Dhttp.nonProxyHosts="172.30.206.*" -Dhttps.nonProxyHosts="172.30.206.*" -Dftp.proxyHost=proxy.eclipse.org -Dftp.proxyPort=9898 -Dftp.nonProxyHosts="172.30.206.*" ANT_ARGS=-Djava.io.tmpdir=/tmp/genie.releng -Dhttp.proxyHost=proxy.eclipse.org -Dhttp.proxyPort=9898 -Dhttps.proxyHost=proxy.eclipse.org -Dhttps.proxyPort=9898 -Dhttp.nonProxyHosts="172.30.206.*" -Dhttps.nonProxyHosts="172.30.206.*" -Dftp.proxyHost=proxy.eclipse.org -Dftp.proxyPort=9898 -Dftp.nonProxyHosts="172.30.206.*"onProxyHosts="*.eclipse.org" -Dftp.proxyHost=proxy.eclipse.org -Dftp.proxyPort=9898 -Dftp.nonProxyHosts="*.eclipse.org" JAVA_PROXIES=-Dhttp.proxyHost=proxy.eclipse.org -Dhttp.proxyPort=9898 -Dhttps.proxyHost=proxy.eclipse.org -Dhttps.proxyPort=9898 -Dhttp.nonProxyHosts="172.30.206.*" -Dhttps.nonProxyHosts="172.30.206.*" -Dftp.proxyHost=proxy.eclipse.org -Dftp.proxyPort=9898 -Dftp.nonProxyHosts="172.30.206.*"
From my (little) experience, I think only these are relevant, so will start off just trying this "minimal" set. ANT_OPTS=-Djava.io.tmpdir=/tmp/genie.releng -Dhttp.proxyHost=proxy.eclipse.org -Dhttp.proxyPort=9898 -Dhttps.proxyHost=proxy.eclipse.org -Dhttps.proxyPort=9898 -Dhttp.nonProxyHosts="172.30.206.*" -Dhttps.nonProxyHosts="172.30.206.*" -Dftp.proxyHost=proxy.eclipse.org -Dftp.proxyPort=9898 -Dftp.nonProxyHosts="172.30.206.*" http_proxy=http://proxy.eclipse.org:9898 ftp_proxy=http://proxy.eclipse.org:9898 Plus, that have some set in maven's settings, which I have not copied over to our own build's settings.xml file (which I have just started to experiment with). So, I'll set these too: <proxies> <proxy> <active>true</active> <protocol>http</protocol> <host>proxy.eclipse.org</host> <port>9898</port> <nonProxyHosts>eclipse.org</nonProxyHosts> </proxy> </proxies>
(In reply to David Williams from comment #3) > Plus, that have some set in maven's settings, which I have not copied over > to our own build's settings.xml file (which I have just started to > experiment with). > > So, I'll set these too: > > <proxies> > <proxy> > <active>true</active> > <protocol>http</protocol> > <host>proxy.eclipse.org</host> > <port>9898</port> > <nonProxyHosts>eclipse.org</nonProxyHosts> > </proxy> > </proxies> Actually, looking back at recent N-builds, I think this started when I started to use "custom settings.xml". So, I think I'll try that first, since that better isolates the settings from the build. (The other case was with a wget command back to another HIPP instance, which has a --no-proxies option and that worked around that problem, for the moment).
(In reply to David Williams from comment #4) > (In reply to David Williams from comment #3) > > > Plus, that have some set in maven's settings, which I have not copied over > > to our own build's settings.xml file (which I have just started to > > experiment with). > > > > So, I'll set these too: > > > > <proxies> > > <proxy> > > <active>true</active> > > <protocol>http</protocol> > > <host>proxy.eclipse.org</host> > > <port>9898</port> > > <nonProxyHosts>eclipse.org</nonProxyHosts> > > </proxy> > > </proxies> > This did not help (adding the "default" to my custom settings.xml) but from the error, and what I've seen on the web, is should also have one for https! (If this works, I'll open a Hudson bug). <proxy> <active>true</active> <protocol>https</protocol> <host>proxy.eclipse.org</host> <port>9898</port> <nonProxyHosts>eclipse.org</nonProxyHosts> </proxy>
(In reply to David Williams from comment #5) > This did not help (adding the "default" to my custom settings.xml) but from > the error, and what I've seen on the web, is should also have one for https! Adding HTTPS to Hudson's setting.xml file did not help either. Next I am trying to add all those variables that define proxy settings so see if it makes a difference. If not, I'll move back to "running from e4Build" for now.
(In reply to David Williams from comment #6) dding HTTPS to Hudson's setting.xml file did not help either. > > Next I am trying to add all those variables that define proxy settings so > see if it makes a difference. If not, I'll move back to "running from > e4Build" for now. Also did not help. I have gone back to running as cron job from e4Build id. That will either fix immediate problem, or make it all the more mysterious.
These do appear fixed in tonight's "nightly": http://download.eclipse.org/eclipse/downloads/drops4/N20160328-2100/logs.php#javadoc I'll have to study this in detail to figure out why it works in one case, but not when ran from Releng HIPP.
