You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by Bryan Pendleton <bp...@gmail.com> on 2018/05/06 01:31:27 UTC
Ant version in Jenkins
Rick, we require Ant version 1.10.2 now?
How do we update the version of Ant that is installed on
on the Jenkins servers?
thanks,
bryan
---------- Forwarded message ----------
From: Apache Jenkins Server <je...@builds.apache.org>
Date: Sat, May 5, 2018 at 4:37 PM
Subject: Build failed in Jenkins: Derby-trunk-suites.All #165
To: derby-dev@db.apache.org, rhillegas@apache.org, bpapache5@geekdom.net
See <https://builds.apache.org/job/Derby-trunk-suites.All/165/display/redirect?page=changes>
Changes:
[bpendleton] DERBY-6988: Update STATUS page for 10.14.2.0
[bpendleton] DERBY-6988: Add 10.14.2.0 to versions table
[bpendleton] DERBY-6988: Checkin 10.14.2.0 jars for upgrade testing
[rhillegas] DERBY-6945: Add a ResourceBundleProvider for the client
messages so that they can be found when Derby is run using a
modulepath; commit
derby-6945-31-aa-clientmessages-ResourceBundleProvider.diff.
------------------------------------------
Started by an SCM change
[EnvInject] - Loading node environment variables.
Building remotely on H30 (ubuntu xenial) in workspace
<https://builds.apache.org/job/Derby-trunk-suites.All/ws/>
Updating https://svn.apache.org/repos/asf/db/derby/code/trunk at
revision '2018-05-05T23:37:06.309 +0000'
U java/testing/org/apache/derbyTesting/functionTests/tests/upgradeTests/OldVersions.java
U java/client/module-info.java
A java/client/org/apache/derby/loc
A java/client/org/apache/derby/loc/client
AU java/client/org/apache/derby/loc/client/clientmessagesProviderImpl.java
U java/build/org/apache/derbyBuild/lastgoodjarcontents/sane.derbyTesting.jar.lastcontents
U java/build/org/apache/derbyBuild/lastgoodjarcontents/sane.derbyclient.jar.lastcontents
U java/build/org/apache/derbyBuild/lastgoodjarcontents/sane.derbytools.jar.lastcontents
U java/build/org/apache/derbyBuild/lastgoodjarcontents/insane.derbyTesting.jar.lastcontents
U java/build/org/apache/derbyBuild/lastgoodjarcontents/insane.derbyclient.jar.lastcontents
A java/shared/org/apache/derby/loc
A java/shared/org/apache/derby/loc/client
A java/shared/org/apache/derby/loc/client/spi
AU java/shared/org/apache/derby/loc/client/spi/clientmessagesProvider.java
U java/shared/module-info.java
U STATUS
U .
At revision 1831011
Updating https://svn.apache.org/repos/asf/db/derby/jars at revision
'2018-05-05T23:37:06.309 +0000'
A 10.14.2.0
AU 10.14.2.0/derbyLocale_pl.jar
AU 10.14.2.0/derbyLocale_it.jar
AU 10.14.2.0/derbyLocale_hu.jar
AU 10.14.2.0/derby.war
AU 10.14.2.0/derbytools.jar
AU 10.14.2.0/derbyLocale_ja_JP.jar
AU 10.14.2.0/derbyrun.jar
AU 10.14.2.0/derbyLocale_ru.jar
AU 10.14.2.0/derbyoptionaltools.jar
AU 10.14.2.0/derbyLocale_zh_TW.jar
AU 10.14.2.0/derbyTesting.jar
AU 10.14.2.0/derbyclient.jar
AU 10.14.2.0/derby.jar
AU 10.14.2.0/derbyLocale_de_DE.jar
AU 10.14.2.0/derbyLocale_zh_CN.jar
AU 10.14.2.0/derbyLocale_cs.jar
AU 10.14.2.0/derbyLocale_ko_KR.jar
AU 10.14.2.0/derbyLocale_pt_BR.jar
AU 10.14.2.0/derbynet.jar
AU 10.14.2.0/derbyLocale_es.jar
AU 10.14.2.0/derbyLocale_fr.jar
At revision 1831011
[locks-and-latches] Checking to see if we really have the locks
[locks-and-latches] Have all the locks, build can start
[Derby-trunk-suites.All] $ /bin/bash -xe /tmp/jenkins2993569736394132251.sh
+ rm -Rf 'trunk/junit_*'
[trunk] $ /home/jenkins/tools/ant/latest/bin/ant clobber all buildjarsclean
Buildfile: <https://builds.apache.org/job/Derby-trunk-suites.All/ws/trunk/build.xml>
clean:
cleangenerated:
cleanstate:
cleanreleasefiles:
clobber:
checkCompilerLevel:
version_check:
BUILD FAILED
<https://builds.apache.org/job/Derby-trunk-suites.All/ws/trunk/build.xml>:66:
FATAL ERROR: The running Ant version, 1.10.1, is too old.
Total time: 0 seconds
Build step 'Invoke Ant' marked build as failure
[locks-and-latches] Releasing all the locks
[locks-and-latches] All the locks released
Recording test results
ERROR: Step ?Publish JUnit test result report? failed: No test report
files were found. Configuration error?
Re: Ant version in Jenkins
Posted by Bryan Pendleton <bp...@gmail.com>.
OK, done.
It's pretty noisy, so we will probably want to remove it as soon
as we decide if it gives us any clues about the Jenkins
failures or not.
thanks,
bryan
On Tue, May 15, 2018 at 5:41 AM, Rick Hillegas <ri...@gmail.com> wrote:
> On 5/14/18 8:06 PM, Bryan Pendleton wrote:
>>
>> For now, perhaps we should just open a bug in JIRA so we can track this?
>>
>> As to how to get more visibility, I think that we could perhaps add a call
>> to
>> 'echoproperties' in our build.xml and then our Jenkins jobs would echo
>> their system configuration to the output logs.
>>
>> Then we could see if we could spot anything unusual in the configuration
>> of the Jenkins slaves that run these jobs (i.e., which operating system,
>> which compiler, etc.)
>>
>> I.e., something like:
>
> This sounds useful. +1
>
>>
>> Index: build.xml
>> ===================================================================
>> --- build.xml (revision 1831532)
>> +++ build.xml (working copy)
>> @@ -44,6 +44,8 @@
>> </not>
>> </condition>
>>
>> +<echoproperties/>
>> +
>> <!-- Targets -->
>>
>> <target
>>
>>
>>
>> On Mon, May 14, 2018 at 4:52 PM, Rick Hillegas <ri...@gmail.com>
>> wrote:
>>>
>>> I have tried running the unit tests under ant via the junit-core target.
>>> But
>>> I am unable to reproduce the error we are seeing in the Jenkins builds.
>>> One
>>> of the tests which is failing (InternationalConnectSimpleDSTest) is
>>> trying
>>> to boot a database whose name is a Chinese character. The database
>>> directory
>>> is the file which incurs the permissions exception. Maybe Jenkins is
>>> running
>>> on a platform which doesn't support Chinese characters in directory
>>> names? I
>>> don't see any bugs in this area. The closest bug I could find is
>>> DERBY-728,
>>> which was a problem with the network protocol layer. I don't know how to
>>> get
>>> more visibility into the error. I tripped over a 404 error when I clicked
>>> on
>>> the artifacts link of the test failure.
>>>
>>>
>>> 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?
>>>>
>>>> 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?
>>>>
>>>> 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?
>>>>
>>>> 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
>>>>
>
Re: Ant version in Jenkins
Posted by Rick Hillegas <ri...@gmail.com>.
On 5/14/18 8:06 PM, Bryan Pendleton wrote:
> For now, perhaps we should just open a bug in JIRA so we can track this?
>
> As to how to get more visibility, I think that we could perhaps add a call to
> 'echoproperties' in our build.xml and then our Jenkins jobs would echo
> their system configuration to the output logs.
>
> Then we could see if we could spot anything unusual in the configuration
> of the Jenkins slaves that run these jobs (i.e., which operating system,
> which compiler, etc.)
>
> I.e., something like:
This sounds useful. +1
>
> Index: build.xml
> ===================================================================
> --- build.xml (revision 1831532)
> +++ build.xml (working copy)
> @@ -44,6 +44,8 @@
> </not>
> </condition>
>
> +<echoproperties/>
> +
> <!-- Targets -->
>
> <target
>
>
>
> On Mon, May 14, 2018 at 4:52 PM, Rick Hillegas <ri...@gmail.com> wrote:
>> I have tried running the unit tests under ant via the junit-core target. But
>> I am unable to reproduce the error we are seeing in the Jenkins builds. One
>> of the tests which is failing (InternationalConnectSimpleDSTest) is trying
>> to boot a database whose name is a Chinese character. The database directory
>> is the file which incurs the permissions exception. Maybe Jenkins is running
>> on a platform which doesn't support Chinese characters in directory names? I
>> don't see any bugs in this area. The closest bug I could find is DERBY-728,
>> which was a problem with the network protocol layer. I don't know how to get
>> more visibility into the error. I tripped over a 404 error when I clicked on
>> the artifacts link of the test failure.
>>
>>
>> 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?
>>>
>>> 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?
>>>
>>> 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?
>>>
>>> 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
>>>
Re: Ant version in Jenkins
Posted by Bryan Pendleton <bp...@gmail.com>.
For now, perhaps we should just open a bug in JIRA so we can track this?
As to how to get more visibility, I think that we could perhaps add a call to
'echoproperties' in our build.xml and then our Jenkins jobs would echo
their system configuration to the output logs.
Then we could see if we could spot anything unusual in the configuration
of the Jenkins slaves that run these jobs (i.e., which operating system,
which compiler, etc.)
I.e., something like:
Index: build.xml
===================================================================
--- build.xml (revision 1831532)
+++ build.xml (working copy)
@@ -44,6 +44,8 @@
</not>
</condition>
+<echoproperties/>
+
<!-- Targets -->
<target
On Mon, May 14, 2018 at 4:52 PM, Rick Hillegas <ri...@gmail.com> wrote:
> I have tried running the unit tests under ant via the junit-core target. But
> I am unable to reproduce the error we are seeing in the Jenkins builds. One
> of the tests which is failing (InternationalConnectSimpleDSTest) is trying
> to boot a database whose name is a Chinese character. The database directory
> is the file which incurs the permissions exception. Maybe Jenkins is running
> on a platform which doesn't support Chinese characters in directory names? I
> don't see any bugs in this area. The closest bug I could find is DERBY-728,
> which was a problem with the network protocol layer. I don't know how to get
> more visibility into the error. I tripped over a 404 error when I clicked on
> the artifacts link of the test failure.
>
>
> 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?
>>
>> 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?
>>
>> 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?
>>
>> 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
>>
>
Re: Ant version in Jenkins
Posted by Rick Hillegas <ri...@gmail.com>.
I have tried running the unit tests under ant via the junit-core target.
But I am unable to reproduce the error we are seeing in the Jenkins
builds. One of the tests which is failing
(InternationalConnectSimpleDSTest) is trying to boot a database whose
name is a Chinese character. The database directory is the file which
incurs the permissions exception. Maybe Jenkins is running on a platform
which doesn't support Chinese characters in directory names? I don't see
any bugs in this area. The closest bug I could find is DERBY-728, which
was a problem with the network protocol layer. I don't know how to get
more visibility into the error. I tripped over a 404 error when I
clicked on the artifacts link of the test failure.
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?
>
> 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?
>
> 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?
>
> 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
>
Re: Ant version in Jenkins
Posted by Rick Hillegas <ri...@gmail.com>.
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
>
Re: Ant version in Jenkins
Posted by Bryan Pendleton <bp...@gmail.com>.
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?
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?
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?
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
Re: Ant version in Jenkins
Posted by Rick Hillegas <ri...@gmail.com>.
The build now succeeds but Jenkins trips over permissions problems when
it runs the following tests:
org.apache.derbyTesting.functionTests.tests.derbynet.ProtocolTest
org.apache.derbyTesting.functionTests.tests.jdbcapi.InternationalConnectSimpleDSTest
org.apache.derbyTesting.functionTests.tests.jdbcapi.InternationalConnectTest
The tests run fine on my machine.
Bryan,
Can you sync to the head of the trunk and run those junit tests?
Thanks,
-Rick
On 5/12/18 11:43 AM, Rick Hillegas wrote:
> Thanks for spotting that Bryan. On my Mac, the spurious character just
> looks like whitespace. I don't know why the build succeeds on my
> machine though. I have removed the spurious character with submission
> 1831487. I hope that fixes the problem.
>
> Thanks,
> -Rick
>
> On 5/12/18 8:37 AM, Bryan Pendleton wrote:
>> No, I think that strange character is in the copy of the file that
>> is checked into subversion:
>>
>> http://svn.apache.org/viewvc/db/derby/code/trunk/java/client/org/apache/derby/loc/client/clientmessagesProviderImpl.java?view=markup
>>
>>
>> Rick, did you change that file recently?
>>
>> thanks,
>>
>> bryan
>>
>>
>> On Sat, May 12, 2018 at 8:35 AM, Bryan Pendleton
>> <bp...@gmail.com> wrote:
>>> On my Windows 10 system, with Java 9.0.4 and the head of trunk, I get
>>> something similar, but not identical.
>>>
>>> compile:
>>> [javac] Compiling 143 source files to
>>> C:\Users\Bryan\derby\trunk\classes\client
>>> [javac]
>>> C:\Users\Bryan\derby\trunk\java\client\org\apache\derby\loc\client\clientmessagesProviderImpl.java:31:
>>> error: illegal character: '\u2039'
>>> [javac] public ResourceBundle getBundleΓÇï(String baseName,
>>> Locale locale)
>>> [javac] ^
>>> [javac]
>>> C:\Users\Bryan\derby\trunk\java\client\org\apache\derby\loc\client\clientmessagesProviderImpl.java:31:
>>> error: ';' expected
>>> [javac] public ResourceBundle getBundleΓÇï(String baseName,
>>> Locale locale)
>>> [javac] ^
>>> [javac]
>>> C:\Users\Bryan\derby\trunk\java\client\org\apache\derby\loc\client\clientmessagesProviderImpl.java:31:
>>> error: <identifier> expected
>>> [javac] public ResourceBundle getBundleΓÇï(String baseName,
>>> Locale locale)
>>> [javac]
>>> ^
>>> [javac]
>>> C:\Users\Bryan\derby\trunk\java\client\org\apache\derby\loc\client\clientmessagesProviderImpl.java:31:
>>> error: cannot find symbol
>>> [javac] public ResourceBundle getBundleΓÇï(String baseName,
>>> Locale locale)
>>> [javac] ^
>>> [javac] symbol: class locale
>>> [javac] location: class clientmessagesProviderImpl
>>> [javac]
>>> C:\Users\Bryan\derby\trunk\java\client\org\apache\derby\loc\client\clientmessagesProviderImpl.java:29:
>>> error: clientmessagesProviderImpl is not abstract and does not
>>> override abstract method getBundle(String,Locale) in
>>> ResourceBundleProvider
>>> [javac] public class clientmessagesProviderImpl implements
>>> clientmessagesProvider
>>> [javac] ^
>>> [javac]
>>> C:\Users\Bryan\derby\trunk\java\client\org\apache\derby\loc\client\clientmessagesProviderImpl.java:33:
>>> error: cannot find symbol
>>> [javac] ResourceBundle bundle =
>>> ResourceBundle.getBundle(baseName, locale);
>>> [javac] ^
>>> [javac] symbol: variable locale
>>> [javac] location: class clientmessagesProviderImpl
>>> [javac]
>>> C:\Users\Bryan\derby\trunk\java\client\org\apache\derby\loc\client\clientmessagesProviderImpl.java:34:
>>> error: return outside method
>>> [javac] return bundle;
>>> [javac] ^
>>> [javac] 7 errors
>>>
>>>
>>> I see the message that Jenkins sees, but I also see some strange
>>> messages. I wonder if I've got some filesystem damage in my tree?
>>>
>>> I'll investigate further...
>>>
>>> bryan
>
>
Re: Ant version in Jenkins
Posted by Rick Hillegas <ri...@gmail.com>.
Thanks for spotting that Bryan. On my Mac, the spurious character just
looks like whitespace. I don't know why the build succeeds on my machine
though. I have removed the spurious character with submission 1831487. I
hope that fixes the problem.
Thanks,
-Rick
On 5/12/18 8:37 AM, Bryan Pendleton wrote:
> No, I think that strange character is in the copy of the file that
> is checked into subversion:
>
> http://svn.apache.org/viewvc/db/derby/code/trunk/java/client/org/apache/derby/loc/client/clientmessagesProviderImpl.java?view=markup
>
> Rick, did you change that file recently?
>
> thanks,
>
> bryan
>
>
> On Sat, May 12, 2018 at 8:35 AM, Bryan Pendleton
> <bp...@gmail.com> wrote:
>> On my Windows 10 system, with Java 9.0.4 and the head of trunk, I get
>> something similar, but not identical.
>>
>> compile:
>> [javac] Compiling 143 source files to
>> C:\Users\Bryan\derby\trunk\classes\client
>> [javac] C:\Users\Bryan\derby\trunk\java\client\org\apache\derby\loc\client\clientmessagesProviderImpl.java:31:
>> error: illegal character: '\u2039'
>> [javac] public ResourceBundle getBundleΓÇï(String baseName,
>> Locale locale)
>> [javac] ^
>> [javac] C:\Users\Bryan\derby\trunk\java\client\org\apache\derby\loc\client\clientmessagesProviderImpl.java:31:
>> error: ';' expected
>> [javac] public ResourceBundle getBundleΓÇï(String baseName,
>> Locale locale)
>> [javac] ^
>> [javac] C:\Users\Bryan\derby\trunk\java\client\org\apache\derby\loc\client\clientmessagesProviderImpl.java:31:
>> error: <identifier> expected
>> [javac] public ResourceBundle getBundleΓÇï(String baseName,
>> Locale locale)
>> [javac]
>> ^
>> [javac] C:\Users\Bryan\derby\trunk\java\client\org\apache\derby\loc\client\clientmessagesProviderImpl.java:31:
>> error: cannot find symbol
>> [javac] public ResourceBundle getBundleΓÇï(String baseName,
>> Locale locale)
>> [javac] ^
>> [javac] symbol: class locale
>> [javac] location: class clientmessagesProviderImpl
>> [javac] C:\Users\Bryan\derby\trunk\java\client\org\apache\derby\loc\client\clientmessagesProviderImpl.java:29:
>> error: clientmessagesProviderImpl is not abstract and does not
>> override abstract method getBundle(String,Locale) in
>> ResourceBundleProvider
>> [javac] public class clientmessagesProviderImpl implements
>> clientmessagesProvider
>> [javac] ^
>> [javac] C:\Users\Bryan\derby\trunk\java\client\org\apache\derby\loc\client\clientmessagesProviderImpl.java:33:
>> error: cannot find symbol
>> [javac] ResourceBundle bundle =
>> ResourceBundle.getBundle(baseName, locale);
>> [javac] ^
>> [javac] symbol: variable locale
>> [javac] location: class clientmessagesProviderImpl
>> [javac] C:\Users\Bryan\derby\trunk\java\client\org\apache\derby\loc\client\clientmessagesProviderImpl.java:34:
>> error: return outside method
>> [javac] return bundle;
>> [javac] ^
>> [javac] 7 errors
>>
>>
>> I see the message that Jenkins sees, but I also see some strange
>> messages. I wonder if I've got some filesystem damage in my tree?
>>
>> I'll investigate further...
>>
>> bryan
Re: Ant version in Jenkins
Posted by Bryan Pendleton <bp...@gmail.com>.
No, I think that strange character is in the copy of the file that
is checked into subversion:
http://svn.apache.org/viewvc/db/derby/code/trunk/java/client/org/apache/derby/loc/client/clientmessagesProviderImpl.java?view=markup
Rick, did you change that file recently?
thanks,
bryan
On Sat, May 12, 2018 at 8:35 AM, Bryan Pendleton
<bp...@gmail.com> wrote:
> On my Windows 10 system, with Java 9.0.4 and the head of trunk, I get
> something similar, but not identical.
>
> compile:
> [javac] Compiling 143 source files to
> C:\Users\Bryan\derby\trunk\classes\client
> [javac] C:\Users\Bryan\derby\trunk\java\client\org\apache\derby\loc\client\clientmessagesProviderImpl.java:31:
> error: illegal character: '\u2039'
> [javac] public ResourceBundle getBundleΓÇï(String baseName,
> Locale locale)
> [javac] ^
> [javac] C:\Users\Bryan\derby\trunk\java\client\org\apache\derby\loc\client\clientmessagesProviderImpl.java:31:
> error: ';' expected
> [javac] public ResourceBundle getBundleΓÇï(String baseName,
> Locale locale)
> [javac] ^
> [javac] C:\Users\Bryan\derby\trunk\java\client\org\apache\derby\loc\client\clientmessagesProviderImpl.java:31:
> error: <identifier> expected
> [javac] public ResourceBundle getBundleΓÇï(String baseName,
> Locale locale)
> [javac]
> ^
> [javac] C:\Users\Bryan\derby\trunk\java\client\org\apache\derby\loc\client\clientmessagesProviderImpl.java:31:
> error: cannot find symbol
> [javac] public ResourceBundle getBundleΓÇï(String baseName,
> Locale locale)
> [javac] ^
> [javac] symbol: class locale
> [javac] location: class clientmessagesProviderImpl
> [javac] C:\Users\Bryan\derby\trunk\java\client\org\apache\derby\loc\client\clientmessagesProviderImpl.java:29:
> error: clientmessagesProviderImpl is not abstract and does not
> override abstract method getBundle(String,Locale) in
> ResourceBundleProvider
> [javac] public class clientmessagesProviderImpl implements
> clientmessagesProvider
> [javac] ^
> [javac] C:\Users\Bryan\derby\trunk\java\client\org\apache\derby\loc\client\clientmessagesProviderImpl.java:33:
> error: cannot find symbol
> [javac] ResourceBundle bundle =
> ResourceBundle.getBundle(baseName, locale);
> [javac] ^
> [javac] symbol: variable locale
> [javac] location: class clientmessagesProviderImpl
> [javac] C:\Users\Bryan\derby\trunk\java\client\org\apache\derby\loc\client\clientmessagesProviderImpl.java:34:
> error: return outside method
> [javac] return bundle;
> [javac] ^
> [javac] 7 errors
>
>
> I see the message that Jenkins sees, but I also see some strange
> messages. I wonder if I've got some filesystem damage in my tree?
>
> I'll investigate further...
>
> bryan
Re: Ant version in Jenkins
Posted by Bryan Pendleton <bp...@gmail.com>.
On my Windows 10 system, with Java 9.0.4 and the head of trunk, I get
something similar, but not identical.
compile:
[javac] Compiling 143 source files to
C:\Users\Bryan\derby\trunk\classes\client
[javac] C:\Users\Bryan\derby\trunk\java\client\org\apache\derby\loc\client\clientmessagesProviderImpl.java:31:
error: illegal character: '\u2039'
[javac] public ResourceBundle getBundleΓÇï(String baseName,
Locale locale)
[javac] ^
[javac] C:\Users\Bryan\derby\trunk\java\client\org\apache\derby\loc\client\clientmessagesProviderImpl.java:31:
error: ';' expected
[javac] public ResourceBundle getBundleΓÇï(String baseName,
Locale locale)
[javac] ^
[javac] C:\Users\Bryan\derby\trunk\java\client\org\apache\derby\loc\client\clientmessagesProviderImpl.java:31:
error: <identifier> expected
[javac] public ResourceBundle getBundleΓÇï(String baseName,
Locale locale)
[javac]
^
[javac] C:\Users\Bryan\derby\trunk\java\client\org\apache\derby\loc\client\clientmessagesProviderImpl.java:31:
error: cannot find symbol
[javac] public ResourceBundle getBundleΓÇï(String baseName,
Locale locale)
[javac] ^
[javac] symbol: class locale
[javac] location: class clientmessagesProviderImpl
[javac] C:\Users\Bryan\derby\trunk\java\client\org\apache\derby\loc\client\clientmessagesProviderImpl.java:29:
error: clientmessagesProviderImpl is not abstract and does not
override abstract method getBundle(String,Locale) in
ResourceBundleProvider
[javac] public class clientmessagesProviderImpl implements
clientmessagesProvider
[javac] ^
[javac] C:\Users\Bryan\derby\trunk\java\client\org\apache\derby\loc\client\clientmessagesProviderImpl.java:33:
error: cannot find symbol
[javac] ResourceBundle bundle =
ResourceBundle.getBundle(baseName, locale);
[javac] ^
[javac] symbol: variable locale
[javac] location: class clientmessagesProviderImpl
[javac] C:\Users\Bryan\derby\trunk\java\client\org\apache\derby\loc\client\clientmessagesProviderImpl.java:34:
error: return outside method
[javac] return bundle;
[javac] ^
[javac] 7 errors
I see the message that Jenkins sees, but I also see some strange
messages. I wonder if I've got some filesystem damage in my tree?
I'll investigate further...
bryan
Re: Ant version in Jenkins
Posted by Rick Hillegas <ri...@gmail.com>.
Thanks for looking into this Bryan. I am confused by these build
results. The build succeeds on my machine but it fails in the Apache
Jenkins environment thusly...
compile:
[javac] Compiling 143 source files to
/home/jenkins/jenkins-slave/workspace/Derby-trunk-suites.All/trunk/classes/client
[javac]
/home/jenkins/jenkins-slave/workspace/Derby-trunk-suites.All/trunk/java/client/org/apache/derby/loc/client/clientmessagesProviderImpl.java:29:
error: clientmessagesProviderImpl is not abstract and does not override
abstract method getBundle(String,Locale) in ResourceBundleProvider
[javac] public class clientmessagesProviderImpl implements
clientmessagesProvider
[javac] ^
[javac] 1 error
Could you sync to the head of the trunk and see what happens on your
machine?
Thanks,
-Rick
On 5/11/18 2:23 PM, Bryan Pendleton wrote:
> It seems like the Jenkins builds are now operational, and are
> producing legitimate output.
>
> Rick, what do you think?
>
> Here's one of the recent runs:
>
> https://builds.apache.org/blue/rest/organizations/jenkins/pipelines/Derby-trunk-suites.All/runs/168/log/?start=0
>
> thanks,
>
> bryan
>
>
>
> On Sun, May 6, 2018 at 9:00 AM, Bryan Pendleton
> <bp...@gmail.com> wrote:
>> When I look here:
>>
>> https://cwiki.apache.org/confluence/display/INFRA/Ant+Installation+Matrix
>>
>> it seems to be saying that the newest version of Ant that is installed
>> on the Jenkins slaves is 1.10.1.
>>
>> I see on ant.apache.org that the Ant team have now released 1.10.3.
>>
>> I'll see if I can figure out where to ask Infra for an upgrade.
>>
>> thanks,
>>
>> bryan
>>
>>
>> On Sun, May 6, 2018 at 7:22 AM, Rick Hillegas <ri...@gmail.com> wrote:
>>> On 5/5/18 6:31 PM, Bryan Pendleton wrote:
>>>> Rick, we require Ant version 1.10.2 now?
>>> I did not make that change to Jenkins. We seem to be running with 1.10.1.
>>>>
>>>> How do we update the version of Ant that is installed on
>>>> on the Jenkins servers?
>>> I'm afraid that I know very little about Jenkins. This is why I have not
>>> touched it. At some point in the past I tried unsuccessfully to update the
>>> Jenkins builds. I don't remember what I did and failed to accomplish.
>>>
>>> I don't see anything useful when I go to the build page at
>>> https://builds.apache.org/view/A-D/view/Derby/job/Derby-trunk-suites.All/
>>>
>>> If I click on a build, I get a screen with some hopeful looking links on the
>>> left. See
>>> https://builds.apache.org/view/A-D/view/Derby/job/Derby-trunk-suites.All/lastBuild/
>>>
>>> Somewhere there is a screen which lets you define the script which the build
>>> runs. I think that screen lets you define the version level of the tools
>>> needed by the script. But I can't find that script now.
>>>
>>> Maybe the links I am looking for are hidden because I haven't clicked on the
>>> "log in" link in the upper right corner and logged in. However, I have
>>> searched through my password vault and I have no record of credentials
>>> created for Jenkins.
>>>
>>> I wouldn't mind doing some light maintenance on our Jenkins setup if I
>>> understood it. But I haven't found the time to read all the Jenkins
>>> documentation and figure this stuff out. Maybe there is a short primer on
>>> our wiki explaining how to maintain Jenkins. I can't find it.
>>>
>>> I would not mind turning off the Jenkins machinery if it is providing no
>>> value and no-one knows how to maintain it. Maybe the exercise of turning
>>> Jenkins off would teach us enough to maintain it.
>>>
>>> Sorry that I don't have anything useful to say.
>>>
>>> -Rick
>>>
>>>> thanks,
>>>>
>>>> bryan
>>>>
>>>>
>>>>
>>>> ---------- Forwarded message ----------
>>>> From: Apache Jenkins Server <je...@builds.apache.org>
>>>> Date: Sat, May 5, 2018 at 4:37 PM
>>>> Subject: Build failed in Jenkins: Derby-trunk-suites.All #165
>>>> To: derby-dev@db.apache.org, rhillegas@apache.org, bpapache5@geekdom.net
>>>>
>>>>
>>>> See
>>>> <https://builds.apache.org/job/Derby-trunk-suites.All/165/display/redirect?page=changes>
>>>>
>>>> Changes:
>>>>
>>>> [bpendleton] DERBY-6988: Update STATUS page for 10.14.2.0
>>>>
>>>> [bpendleton] DERBY-6988: Add 10.14.2.0 to versions table
>>>>
>>>> [bpendleton] DERBY-6988: Checkin 10.14.2.0 jars for upgrade testing
>>>>
>>>> [rhillegas] DERBY-6945: Add a ResourceBundleProvider for the client
>>>> messages so that they can be found when Derby is run using a
>>>> modulepath; commit
>>>> derby-6945-31-aa-clientmessages-ResourceBundleProvider.diff.
>>>>
>>>> ------------------------------------------
>>>> Started by an SCM change
>>>> [EnvInject] - Loading node environment variables.
>>>> Building remotely on H30 (ubuntu xenial) in workspace
>>>> <https://builds.apache.org/job/Derby-trunk-suites.All/ws/>
>>>> Updating https://svn.apache.org/repos/asf/db/derby/code/trunk at
>>>> revision '2018-05-05T23:37:06.309 +0000'
>>>> U
>>>> java/testing/org/apache/derbyTesting/functionTests/tests/upgradeTests/OldVersions.java
>>>> U java/client/module-info.java
>>>> A java/client/org/apache/derby/loc
>>>> A java/client/org/apache/derby/loc/client
>>>> AU
>>>> java/client/org/apache/derby/loc/client/clientmessagesProviderImpl.java
>>>> U
>>>> java/build/org/apache/derbyBuild/lastgoodjarcontents/sane.derbyTesting.jar.lastcontents
>>>> U
>>>> java/build/org/apache/derbyBuild/lastgoodjarcontents/sane.derbyclient.jar.lastcontents
>>>> U
>>>> java/build/org/apache/derbyBuild/lastgoodjarcontents/sane.derbytools.jar.lastcontents
>>>> U
>>>> java/build/org/apache/derbyBuild/lastgoodjarcontents/insane.derbyTesting.jar.lastcontents
>>>> U
>>>> java/build/org/apache/derbyBuild/lastgoodjarcontents/insane.derbyclient.jar.lastcontents
>>>> A java/shared/org/apache/derby/loc
>>>> A java/shared/org/apache/derby/loc/client
>>>> A java/shared/org/apache/derby/loc/client/spi
>>>> AU
>>>> java/shared/org/apache/derby/loc/client/spi/clientmessagesProvider.java
>>>> U java/shared/module-info.java
>>>> U STATUS
>>>> U .
>>>> At revision 1831011
>>>>
>>>> Updating https://svn.apache.org/repos/asf/db/derby/jars at revision
>>>> '2018-05-05T23:37:06.309 +0000'
>>>> A 10.14.2.0
>>>> AU 10.14.2.0/derbyLocale_pl.jar
>>>> AU 10.14.2.0/derbyLocale_it.jar
>>>> AU 10.14.2.0/derbyLocale_hu.jar
>>>> AU 10.14.2.0/derby.war
>>>> AU 10.14.2.0/derbytools.jar
>>>> AU 10.14.2.0/derbyLocale_ja_JP.jar
>>>> AU 10.14.2.0/derbyrun.jar
>>>> AU 10.14.2.0/derbyLocale_ru.jar
>>>> AU 10.14.2.0/derbyoptionaltools.jar
>>>> AU 10.14.2.0/derbyLocale_zh_TW.jar
>>>> AU 10.14.2.0/derbyTesting.jar
>>>> AU 10.14.2.0/derbyclient.jar
>>>> AU 10.14.2.0/derby.jar
>>>> AU 10.14.2.0/derbyLocale_de_DE.jar
>>>> AU 10.14.2.0/derbyLocale_zh_CN.jar
>>>> AU 10.14.2.0/derbyLocale_cs.jar
>>>> AU 10.14.2.0/derbyLocale_ko_KR.jar
>>>> AU 10.14.2.0/derbyLocale_pt_BR.jar
>>>> AU 10.14.2.0/derbynet.jar
>>>> AU 10.14.2.0/derbyLocale_es.jar
>>>> AU 10.14.2.0/derbyLocale_fr.jar
>>>> At revision 1831011
>>>>
>>>> [locks-and-latches] Checking to see if we really have the locks
>>>> [locks-and-latches] Have all the locks, build can start
>>>> [Derby-trunk-suites.All] $ /bin/bash -xe
>>>> /tmp/jenkins2993569736394132251.sh
>>>> + rm -Rf 'trunk/junit_*'
>>>> [trunk] $ /home/jenkins/tools/ant/latest/bin/ant clobber all
>>>> buildjarsclean
>>>> Buildfile:
>>>> <https://builds.apache.org/job/Derby-trunk-suites.All/ws/trunk/build.xml>
>>>>
>>>> clean:
>>>>
>>>> cleangenerated:
>>>>
>>>> cleanstate:
>>>>
>>>> cleanreleasefiles:
>>>>
>>>> clobber:
>>>>
>>>> checkCompilerLevel:
>>>>
>>>> version_check:
>>>>
>>>> BUILD FAILED
>>>>
>>>> <https://builds.apache.org/job/Derby-trunk-suites.All/ws/trunk/build.xml>:66:
>>>> FATAL ERROR: The running Ant version, 1.10.1, is too old.
>>>>
>>>> Total time: 0 seconds
>>>> Build step 'Invoke Ant' marked build as failure
>>>> [locks-and-latches] Releasing all the locks
>>>> [locks-and-latches] All the locks released
>>>> Recording test results
>>>> ERROR: Step ?Publish JUnit test result report? failed: No test report
>>>> files were found. Configuration error?
>>>>
Re: Ant version in Jenkins
Posted by Bryan Pendleton <bp...@gmail.com>.
It seems like the Jenkins builds are now operational, and are
producing legitimate output.
Rick, what do you think?
Here's one of the recent runs:
https://builds.apache.org/blue/rest/organizations/jenkins/pipelines/Derby-trunk-suites.All/runs/168/log/?start=0
thanks,
bryan
On Sun, May 6, 2018 at 9:00 AM, Bryan Pendleton
<bp...@gmail.com> wrote:
> When I look here:
>
> https://cwiki.apache.org/confluence/display/INFRA/Ant+Installation+Matrix
>
> it seems to be saying that the newest version of Ant that is installed
> on the Jenkins slaves is 1.10.1.
>
> I see on ant.apache.org that the Ant team have now released 1.10.3.
>
> I'll see if I can figure out where to ask Infra for an upgrade.
>
> thanks,
>
> bryan
>
>
> On Sun, May 6, 2018 at 7:22 AM, Rick Hillegas <ri...@gmail.com> wrote:
>> On 5/5/18 6:31 PM, Bryan Pendleton wrote:
>>>
>>> Rick, we require Ant version 1.10.2 now?
>>
>> I did not make that change to Jenkins. We seem to be running with 1.10.1.
>>>
>>>
>>> How do we update the version of Ant that is installed on
>>> on the Jenkins servers?
>>
>> I'm afraid that I know very little about Jenkins. This is why I have not
>> touched it. At some point in the past I tried unsuccessfully to update the
>> Jenkins builds. I don't remember what I did and failed to accomplish.
>>
>> I don't see anything useful when I go to the build page at
>> https://builds.apache.org/view/A-D/view/Derby/job/Derby-trunk-suites.All/
>>
>> If I click on a build, I get a screen with some hopeful looking links on the
>> left. See
>> https://builds.apache.org/view/A-D/view/Derby/job/Derby-trunk-suites.All/lastBuild/
>>
>> Somewhere there is a screen which lets you define the script which the build
>> runs. I think that screen lets you define the version level of the tools
>> needed by the script. But I can't find that script now.
>>
>> Maybe the links I am looking for are hidden because I haven't clicked on the
>> "log in" link in the upper right corner and logged in. However, I have
>> searched through my password vault and I have no record of credentials
>> created for Jenkins.
>>
>> I wouldn't mind doing some light maintenance on our Jenkins setup if I
>> understood it. But I haven't found the time to read all the Jenkins
>> documentation and figure this stuff out. Maybe there is a short primer on
>> our wiki explaining how to maintain Jenkins. I can't find it.
>>
>> I would not mind turning off the Jenkins machinery if it is providing no
>> value and no-one knows how to maintain it. Maybe the exercise of turning
>> Jenkins off would teach us enough to maintain it.
>>
>> Sorry that I don't have anything useful to say.
>>
>> -Rick
>>
>>>
>>> thanks,
>>>
>>> bryan
>>>
>>>
>>>
>>> ---------- Forwarded message ----------
>>> From: Apache Jenkins Server <je...@builds.apache.org>
>>> Date: Sat, May 5, 2018 at 4:37 PM
>>> Subject: Build failed in Jenkins: Derby-trunk-suites.All #165
>>> To: derby-dev@db.apache.org, rhillegas@apache.org, bpapache5@geekdom.net
>>>
>>>
>>> See
>>> <https://builds.apache.org/job/Derby-trunk-suites.All/165/display/redirect?page=changes>
>>>
>>> Changes:
>>>
>>> [bpendleton] DERBY-6988: Update STATUS page for 10.14.2.0
>>>
>>> [bpendleton] DERBY-6988: Add 10.14.2.0 to versions table
>>>
>>> [bpendleton] DERBY-6988: Checkin 10.14.2.0 jars for upgrade testing
>>>
>>> [rhillegas] DERBY-6945: Add a ResourceBundleProvider for the client
>>> messages so that they can be found when Derby is run using a
>>> modulepath; commit
>>> derby-6945-31-aa-clientmessages-ResourceBundleProvider.diff.
>>>
>>> ------------------------------------------
>>> Started by an SCM change
>>> [EnvInject] - Loading node environment variables.
>>> Building remotely on H30 (ubuntu xenial) in workspace
>>> <https://builds.apache.org/job/Derby-trunk-suites.All/ws/>
>>> Updating https://svn.apache.org/repos/asf/db/derby/code/trunk at
>>> revision '2018-05-05T23:37:06.309 +0000'
>>> U
>>> java/testing/org/apache/derbyTesting/functionTests/tests/upgradeTests/OldVersions.java
>>> U java/client/module-info.java
>>> A java/client/org/apache/derby/loc
>>> A java/client/org/apache/derby/loc/client
>>> AU
>>> java/client/org/apache/derby/loc/client/clientmessagesProviderImpl.java
>>> U
>>> java/build/org/apache/derbyBuild/lastgoodjarcontents/sane.derbyTesting.jar.lastcontents
>>> U
>>> java/build/org/apache/derbyBuild/lastgoodjarcontents/sane.derbyclient.jar.lastcontents
>>> U
>>> java/build/org/apache/derbyBuild/lastgoodjarcontents/sane.derbytools.jar.lastcontents
>>> U
>>> java/build/org/apache/derbyBuild/lastgoodjarcontents/insane.derbyTesting.jar.lastcontents
>>> U
>>> java/build/org/apache/derbyBuild/lastgoodjarcontents/insane.derbyclient.jar.lastcontents
>>> A java/shared/org/apache/derby/loc
>>> A java/shared/org/apache/derby/loc/client
>>> A java/shared/org/apache/derby/loc/client/spi
>>> AU
>>> java/shared/org/apache/derby/loc/client/spi/clientmessagesProvider.java
>>> U java/shared/module-info.java
>>> U STATUS
>>> U .
>>> At revision 1831011
>>>
>>> Updating https://svn.apache.org/repos/asf/db/derby/jars at revision
>>> '2018-05-05T23:37:06.309 +0000'
>>> A 10.14.2.0
>>> AU 10.14.2.0/derbyLocale_pl.jar
>>> AU 10.14.2.0/derbyLocale_it.jar
>>> AU 10.14.2.0/derbyLocale_hu.jar
>>> AU 10.14.2.0/derby.war
>>> AU 10.14.2.0/derbytools.jar
>>> AU 10.14.2.0/derbyLocale_ja_JP.jar
>>> AU 10.14.2.0/derbyrun.jar
>>> AU 10.14.2.0/derbyLocale_ru.jar
>>> AU 10.14.2.0/derbyoptionaltools.jar
>>> AU 10.14.2.0/derbyLocale_zh_TW.jar
>>> AU 10.14.2.0/derbyTesting.jar
>>> AU 10.14.2.0/derbyclient.jar
>>> AU 10.14.2.0/derby.jar
>>> AU 10.14.2.0/derbyLocale_de_DE.jar
>>> AU 10.14.2.0/derbyLocale_zh_CN.jar
>>> AU 10.14.2.0/derbyLocale_cs.jar
>>> AU 10.14.2.0/derbyLocale_ko_KR.jar
>>> AU 10.14.2.0/derbyLocale_pt_BR.jar
>>> AU 10.14.2.0/derbynet.jar
>>> AU 10.14.2.0/derbyLocale_es.jar
>>> AU 10.14.2.0/derbyLocale_fr.jar
>>> At revision 1831011
>>>
>>> [locks-and-latches] Checking to see if we really have the locks
>>> [locks-and-latches] Have all the locks, build can start
>>> [Derby-trunk-suites.All] $ /bin/bash -xe
>>> /tmp/jenkins2993569736394132251.sh
>>> + rm -Rf 'trunk/junit_*'
>>> [trunk] $ /home/jenkins/tools/ant/latest/bin/ant clobber all
>>> buildjarsclean
>>> Buildfile:
>>> <https://builds.apache.org/job/Derby-trunk-suites.All/ws/trunk/build.xml>
>>>
>>> clean:
>>>
>>> cleangenerated:
>>>
>>> cleanstate:
>>>
>>> cleanreleasefiles:
>>>
>>> clobber:
>>>
>>> checkCompilerLevel:
>>>
>>> version_check:
>>>
>>> BUILD FAILED
>>>
>>> <https://builds.apache.org/job/Derby-trunk-suites.All/ws/trunk/build.xml>:66:
>>> FATAL ERROR: The running Ant version, 1.10.1, is too old.
>>>
>>> Total time: 0 seconds
>>> Build step 'Invoke Ant' marked build as failure
>>> [locks-and-latches] Releasing all the locks
>>> [locks-and-latches] All the locks released
>>> Recording test results
>>> ERROR: Step ?Publish JUnit test result report? failed: No test report
>>> files were found. Configuration error?
>>>
>>
Re: Ant version in Jenkins
Posted by Bryan Pendleton <bp...@gmail.com>.
When I look here:
https://cwiki.apache.org/confluence/display/INFRA/Ant+Installation+Matrix
it seems to be saying that the newest version of Ant that is installed
on the Jenkins slaves is 1.10.1.
I see on ant.apache.org that the Ant team have now released 1.10.3.
I'll see if I can figure out where to ask Infra for an upgrade.
thanks,
bryan
On Sun, May 6, 2018 at 7:22 AM, Rick Hillegas <ri...@gmail.com> wrote:
> On 5/5/18 6:31 PM, Bryan Pendleton wrote:
>>
>> Rick, we require Ant version 1.10.2 now?
>
> I did not make that change to Jenkins. We seem to be running with 1.10.1.
>>
>>
>> How do we update the version of Ant that is installed on
>> on the Jenkins servers?
>
> I'm afraid that I know very little about Jenkins. This is why I have not
> touched it. At some point in the past I tried unsuccessfully to update the
> Jenkins builds. I don't remember what I did and failed to accomplish.
>
> I don't see anything useful when I go to the build page at
> https://builds.apache.org/view/A-D/view/Derby/job/Derby-trunk-suites.All/
>
> If I click on a build, I get a screen with some hopeful looking links on the
> left. See
> https://builds.apache.org/view/A-D/view/Derby/job/Derby-trunk-suites.All/lastBuild/
>
> Somewhere there is a screen which lets you define the script which the build
> runs. I think that screen lets you define the version level of the tools
> needed by the script. But I can't find that script now.
>
> Maybe the links I am looking for are hidden because I haven't clicked on the
> "log in" link in the upper right corner and logged in. However, I have
> searched through my password vault and I have no record of credentials
> created for Jenkins.
>
> I wouldn't mind doing some light maintenance on our Jenkins setup if I
> understood it. But I haven't found the time to read all the Jenkins
> documentation and figure this stuff out. Maybe there is a short primer on
> our wiki explaining how to maintain Jenkins. I can't find it.
>
> I would not mind turning off the Jenkins machinery if it is providing no
> value and no-one knows how to maintain it. Maybe the exercise of turning
> Jenkins off would teach us enough to maintain it.
>
> Sorry that I don't have anything useful to say.
>
> -Rick
>
>>
>> thanks,
>>
>> bryan
>>
>>
>>
>> ---------- Forwarded message ----------
>> From: Apache Jenkins Server <je...@builds.apache.org>
>> Date: Sat, May 5, 2018 at 4:37 PM
>> Subject: Build failed in Jenkins: Derby-trunk-suites.All #165
>> To: derby-dev@db.apache.org, rhillegas@apache.org, bpapache5@geekdom.net
>>
>>
>> See
>> <https://builds.apache.org/job/Derby-trunk-suites.All/165/display/redirect?page=changes>
>>
>> Changes:
>>
>> [bpendleton] DERBY-6988: Update STATUS page for 10.14.2.0
>>
>> [bpendleton] DERBY-6988: Add 10.14.2.0 to versions table
>>
>> [bpendleton] DERBY-6988: Checkin 10.14.2.0 jars for upgrade testing
>>
>> [rhillegas] DERBY-6945: Add a ResourceBundleProvider for the client
>> messages so that they can be found when Derby is run using a
>> modulepath; commit
>> derby-6945-31-aa-clientmessages-ResourceBundleProvider.diff.
>>
>> ------------------------------------------
>> Started by an SCM change
>> [EnvInject] - Loading node environment variables.
>> Building remotely on H30 (ubuntu xenial) in workspace
>> <https://builds.apache.org/job/Derby-trunk-suites.All/ws/>
>> Updating https://svn.apache.org/repos/asf/db/derby/code/trunk at
>> revision '2018-05-05T23:37:06.309 +0000'
>> U
>> java/testing/org/apache/derbyTesting/functionTests/tests/upgradeTests/OldVersions.java
>> U java/client/module-info.java
>> A java/client/org/apache/derby/loc
>> A java/client/org/apache/derby/loc/client
>> AU
>> java/client/org/apache/derby/loc/client/clientmessagesProviderImpl.java
>> U
>> java/build/org/apache/derbyBuild/lastgoodjarcontents/sane.derbyTesting.jar.lastcontents
>> U
>> java/build/org/apache/derbyBuild/lastgoodjarcontents/sane.derbyclient.jar.lastcontents
>> U
>> java/build/org/apache/derbyBuild/lastgoodjarcontents/sane.derbytools.jar.lastcontents
>> U
>> java/build/org/apache/derbyBuild/lastgoodjarcontents/insane.derbyTesting.jar.lastcontents
>> U
>> java/build/org/apache/derbyBuild/lastgoodjarcontents/insane.derbyclient.jar.lastcontents
>> A java/shared/org/apache/derby/loc
>> A java/shared/org/apache/derby/loc/client
>> A java/shared/org/apache/derby/loc/client/spi
>> AU
>> java/shared/org/apache/derby/loc/client/spi/clientmessagesProvider.java
>> U java/shared/module-info.java
>> U STATUS
>> U .
>> At revision 1831011
>>
>> Updating https://svn.apache.org/repos/asf/db/derby/jars at revision
>> '2018-05-05T23:37:06.309 +0000'
>> A 10.14.2.0
>> AU 10.14.2.0/derbyLocale_pl.jar
>> AU 10.14.2.0/derbyLocale_it.jar
>> AU 10.14.2.0/derbyLocale_hu.jar
>> AU 10.14.2.0/derby.war
>> AU 10.14.2.0/derbytools.jar
>> AU 10.14.2.0/derbyLocale_ja_JP.jar
>> AU 10.14.2.0/derbyrun.jar
>> AU 10.14.2.0/derbyLocale_ru.jar
>> AU 10.14.2.0/derbyoptionaltools.jar
>> AU 10.14.2.0/derbyLocale_zh_TW.jar
>> AU 10.14.2.0/derbyTesting.jar
>> AU 10.14.2.0/derbyclient.jar
>> AU 10.14.2.0/derby.jar
>> AU 10.14.2.0/derbyLocale_de_DE.jar
>> AU 10.14.2.0/derbyLocale_zh_CN.jar
>> AU 10.14.2.0/derbyLocale_cs.jar
>> AU 10.14.2.0/derbyLocale_ko_KR.jar
>> AU 10.14.2.0/derbyLocale_pt_BR.jar
>> AU 10.14.2.0/derbynet.jar
>> AU 10.14.2.0/derbyLocale_es.jar
>> AU 10.14.2.0/derbyLocale_fr.jar
>> At revision 1831011
>>
>> [locks-and-latches] Checking to see if we really have the locks
>> [locks-and-latches] Have all the locks, build can start
>> [Derby-trunk-suites.All] $ /bin/bash -xe
>> /tmp/jenkins2993569736394132251.sh
>> + rm -Rf 'trunk/junit_*'
>> [trunk] $ /home/jenkins/tools/ant/latest/bin/ant clobber all
>> buildjarsclean
>> Buildfile:
>> <https://builds.apache.org/job/Derby-trunk-suites.All/ws/trunk/build.xml>
>>
>> clean:
>>
>> cleangenerated:
>>
>> cleanstate:
>>
>> cleanreleasefiles:
>>
>> clobber:
>>
>> checkCompilerLevel:
>>
>> version_check:
>>
>> BUILD FAILED
>>
>> <https://builds.apache.org/job/Derby-trunk-suites.All/ws/trunk/build.xml>:66:
>> FATAL ERROR: The running Ant version, 1.10.1, is too old.
>>
>> Total time: 0 seconds
>> Build step 'Invoke Ant' marked build as failure
>> [locks-and-latches] Releasing all the locks
>> [locks-and-latches] All the locks released
>> Recording test results
>> ERROR: Step ?Publish JUnit test result report? failed: No test report
>> files were found. Configuration error?
>>
>
Re: Ant version in Jenkins
Posted by Rick Hillegas <ri...@gmail.com>.
On 5/5/18 6:31 PM, Bryan Pendleton wrote:
> Rick, we require Ant version 1.10.2 now?
I did not make that change to Jenkins. We seem to be running with 1.10.1.
>
> How do we update the version of Ant that is installed on
> on the Jenkins servers?
I'm afraid that I know very little about Jenkins. This is why I have not
touched it. At some point in the past I tried unsuccessfully to update
the Jenkins builds. I don't remember what I did and failed to accomplish.
I don't see anything useful when I go to the build page at
https://builds.apache.org/view/A-D/view/Derby/job/Derby-trunk-suites.All/
If I click on a build, I get a screen with some hopeful looking links on
the left. See
https://builds.apache.org/view/A-D/view/Derby/job/Derby-trunk-suites.All/lastBuild/
Somewhere there is a screen which lets you define the script which the
build runs. I think that screen lets you define the version level of the
tools needed by the script. But I can't find that script now.
Maybe the links I am looking for are hidden because I haven't clicked on
the "log in" link in the upper right corner and logged in. However, I
have searched through my password vault and I have no record of
credentials created for Jenkins.
I wouldn't mind doing some light maintenance on our Jenkins setup if I
understood it. But I haven't found the time to read all the Jenkins
documentation and figure this stuff out. Maybe there is a short primer
on our wiki explaining how to maintain Jenkins. I can't find it.
I would not mind turning off the Jenkins machinery if it is providing no
value and no-one knows how to maintain it. Maybe the exercise of turning
Jenkins off would teach us enough to maintain it.
Sorry that I don't have anything useful to say.
-Rick
>
> thanks,
>
> bryan
>
>
>
> ---------- Forwarded message ----------
> From: Apache Jenkins Server <je...@builds.apache.org>
> Date: Sat, May 5, 2018 at 4:37 PM
> Subject: Build failed in Jenkins: Derby-trunk-suites.All #165
> To: derby-dev@db.apache.org, rhillegas@apache.org, bpapache5@geekdom.net
>
>
> See <https://builds.apache.org/job/Derby-trunk-suites.All/165/display/redirect?page=changes>
>
> Changes:
>
> [bpendleton] DERBY-6988: Update STATUS page for 10.14.2.0
>
> [bpendleton] DERBY-6988: Add 10.14.2.0 to versions table
>
> [bpendleton] DERBY-6988: Checkin 10.14.2.0 jars for upgrade testing
>
> [rhillegas] DERBY-6945: Add a ResourceBundleProvider for the client
> messages so that they can be found when Derby is run using a
> modulepath; commit
> derby-6945-31-aa-clientmessages-ResourceBundleProvider.diff.
>
> ------------------------------------------
> Started by an SCM change
> [EnvInject] - Loading node environment variables.
> Building remotely on H30 (ubuntu xenial) in workspace
> <https://builds.apache.org/job/Derby-trunk-suites.All/ws/>
> Updating https://svn.apache.org/repos/asf/db/derby/code/trunk at
> revision '2018-05-05T23:37:06.309 +0000'
> U java/testing/org/apache/derbyTesting/functionTests/tests/upgradeTests/OldVersions.java
> U java/client/module-info.java
> A java/client/org/apache/derby/loc
> A java/client/org/apache/derby/loc/client
> AU java/client/org/apache/derby/loc/client/clientmessagesProviderImpl.java
> U java/build/org/apache/derbyBuild/lastgoodjarcontents/sane.derbyTesting.jar.lastcontents
> U java/build/org/apache/derbyBuild/lastgoodjarcontents/sane.derbyclient.jar.lastcontents
> U java/build/org/apache/derbyBuild/lastgoodjarcontents/sane.derbytools.jar.lastcontents
> U java/build/org/apache/derbyBuild/lastgoodjarcontents/insane.derbyTesting.jar.lastcontents
> U java/build/org/apache/derbyBuild/lastgoodjarcontents/insane.derbyclient.jar.lastcontents
> A java/shared/org/apache/derby/loc
> A java/shared/org/apache/derby/loc/client
> A java/shared/org/apache/derby/loc/client/spi
> AU java/shared/org/apache/derby/loc/client/spi/clientmessagesProvider.java
> U java/shared/module-info.java
> U STATUS
> U .
> At revision 1831011
>
> Updating https://svn.apache.org/repos/asf/db/derby/jars at revision
> '2018-05-05T23:37:06.309 +0000'
> A 10.14.2.0
> AU 10.14.2.0/derbyLocale_pl.jar
> AU 10.14.2.0/derbyLocale_it.jar
> AU 10.14.2.0/derbyLocale_hu.jar
> AU 10.14.2.0/derby.war
> AU 10.14.2.0/derbytools.jar
> AU 10.14.2.0/derbyLocale_ja_JP.jar
> AU 10.14.2.0/derbyrun.jar
> AU 10.14.2.0/derbyLocale_ru.jar
> AU 10.14.2.0/derbyoptionaltools.jar
> AU 10.14.2.0/derbyLocale_zh_TW.jar
> AU 10.14.2.0/derbyTesting.jar
> AU 10.14.2.0/derbyclient.jar
> AU 10.14.2.0/derby.jar
> AU 10.14.2.0/derbyLocale_de_DE.jar
> AU 10.14.2.0/derbyLocale_zh_CN.jar
> AU 10.14.2.0/derbyLocale_cs.jar
> AU 10.14.2.0/derbyLocale_ko_KR.jar
> AU 10.14.2.0/derbyLocale_pt_BR.jar
> AU 10.14.2.0/derbynet.jar
> AU 10.14.2.0/derbyLocale_es.jar
> AU 10.14.2.0/derbyLocale_fr.jar
> At revision 1831011
>
> [locks-and-latches] Checking to see if we really have the locks
> [locks-and-latches] Have all the locks, build can start
> [Derby-trunk-suites.All] $ /bin/bash -xe /tmp/jenkins2993569736394132251.sh
> + rm -Rf 'trunk/junit_*'
> [trunk] $ /home/jenkins/tools/ant/latest/bin/ant clobber all buildjarsclean
> Buildfile: <https://builds.apache.org/job/Derby-trunk-suites.All/ws/trunk/build.xml>
>
> clean:
>
> cleangenerated:
>
> cleanstate:
>
> cleanreleasefiles:
>
> clobber:
>
> checkCompilerLevel:
>
> version_check:
>
> BUILD FAILED
> <https://builds.apache.org/job/Derby-trunk-suites.All/ws/trunk/build.xml>:66:
> FATAL ERROR: The running Ant version, 1.10.1, is too old.
>
> Total time: 0 seconds
> Build step 'Invoke Ant' marked build as failure
> [locks-and-latches] Releasing all the locks
> [locks-and-latches] All the locks released
> Recording test results
> ERROR: Step ?Publish JUnit test result report? failed: No test report
> files were found. Configuration error?
>