You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by Christopher Schultz <ch...@christopherschultz.net> on 2019/01/05 21:25:39 UTC
Re: buildbot failure in on tomcat-85-trunk
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
All,
Hmm... this my fault. The EncryptInterceptor tests pass on my local
machine but not on the buildbot server, apparently.
How can I get the log file from the test failure? junit's stdout isn't
enough.
Thanks,
- -chris
On 1/5/19 16:14, buildbot@apache.org wrote:
> The Buildbot has detected a new failure on builder tomcat-85-trunk
> while building . Full details are available at:
> https://ci.apache.org/builders/tomcat-85-trunk/builds/1594
>
> Buildbot URL: https://ci.apache.org/
>
> Buildslave for this Build: silvanus_ubuntu
>
> Build Reason: The AnyBranchScheduler scheduler named
> 'on-tomcat-85-commit' triggered this build Build Source Stamp:
> [branch tomcat/tc8.5.x/trunk] 1850509 Blamelist: schultz
>
> BUILD FAILED: failed compile_1
>
> Sincerely, -The Buildbot
>
>
>
>
> ---------------------------------------------------------------------
>
>
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: dev-help@tomcat.apache.org
>
-----BEGIN PGP SIGNATURE-----
Comment: Using GnuPG with Thunderbird - https://www.enigmail.net/
iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAlwxINIACgkQHPApP6U8
pFj4GA/+KXvQ7j2uEBYCQwrjBlhwysY91po20YS/YVvNmduhH1ieFU64ZfKAO0j8
zqQJhLuOv25Gr1R8HPbZps8RA10lCR8hrYldwywVMUCDsvdgk0qzMGYU+d4/ImTq
K0icX2PRQ3lKF1l1FpSovkot+/5nWwq5jnjpw0+dD9QjqcDUBGqTSA9VSOh18K1Q
/K+tOBUA0bKtHp2XpHUHANFNU7E9PdQHt9HaB0xEU6/X/82UeKvITXNO9dFfeB1G
1H7vSI8LN1kMpMnF2N8AnlW5/GiweKCfO88NancxlSC+SBItwXlIqXtzLxD9/O4T
zS0RyI8j6SGdcLLWz1yLhOTw5LgrNxYNDw+mRVT2SHwo2Fx6WObonP0rOeipLgFU
1JeNRgOM6LZE3ElNQmpthq8z4GDIleT76hxeAkexq4GdYTdceAmx1vCLDhbcsH7Y
I61dCnP7fwivRx2lzX6OjHwjPuPm2UDZ/tzONWaPANG3XaAxlzuiUfNgDTjj5Nwy
tMtVRMIzgXKUntwxhXuQ9YNzOA80AnTbRrghglubAEa18RgQDubVE4ZjxHZ0HUs/
49y70hGFnYlWHby1afT+/pn5RPffTpL94sTSfLoMiPaV1AuEGB8efHp0gDhI5u3p
exqzRuZ906ZsDq/lzASVktU2DhmH1zL84pccG9SQG59qwWUEbrY=
=8qKk
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: buildbot failure in on tomcat-85-trunk
Posted by Christopher Schultz <ch...@christopherschultz.net>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Rainer,
On 1/6/19 10:09, Rainer Jung wrote:
> Hi Chris,
>
> Am 05.01.2019 um 22:25 schrieb Christopher Schultz:
>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
>>
>> All,
>>
>> Hmm... this my fault. The EncryptInterceptor tests pass on my
>> local machine but not on the buildbot server, apparently.
>>
>> How can I get the log file from the test failure? junit's stdout
>> isn't enough.
>
> Not the answer to your question, but the test fails for me as well
> - if I run them using Java 7. For 8 they run fine.
>
> Errors with Java 7 (same errors for all three connectors, I get
> the errors on Solaris and eg. on RHEL 7 using Oracle HotSpot JDK
> 1.7.80):
>
> Testsuite:
> org.apache.catalina.tribes.group.interceptors.TestEncryptInterceptor
>
>
Tests run: 18, Failures: 0, Errors: 3, Skipped: 2, Time elapsed: 2.375 s
ec
> ------------- Standard Error ----------------- 06-Jan-2019
> 15:20:11.215 SEVERE [main]
> org.apache.catalina.tribes.group.interceptors.EncryptInterceptor.sendM
essage
>
>
Failed to encrypt message
> 06-Jan-2019 15:20:11.252 SEVERE [main]
> org.apache.catalina.tribes.group.interceptors.EncryptInterceptor.sendM
essage
>
>
Failed to encrypt message
> File message.bin does not exist. Skipping test. -------------
> ---------------- ---------------
>
> Testcase: test192BitKey took 1.281 sec Caused an ERROR
> java.security.InvalidKeyException: Illegal key size; No faulty
> members identified. org.apache.catalina.tribes.ChannelException:
> java.security.InvalidKeyException: Illegal key size; No faulty
> members identified.
Oh... I'll bet that's a problem with the "limited crypto" garbage.
I can skip the test if the keys are too long. I'll add that.
> Caused by: java.security.NoSuchAlgorithmException: Unsupported mode
> GCM at
> sun.security.pkcs11.P11Cipher.engineSetMode(P11Cipher.java:202) at
> javax.crypto.Cipher$Transform.setModePadding(Cipher.java:362) at
> javax.crypto.Cipher.getInstance(Cipher.java:522)
Right, also lack of GCM in older JVMs. I can detect-and-skip that
test, too.
> The first two errors can be fixed by installing the "Java
> Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy
> Files" for Java 7. The third one is probably due to the use of an
> algorithm that's simply not available for the latest free Java 7.
>
> Probably the build slave observed the same problem(s).
Thanks for the analysis.
- -chris
-----BEGIN PGP SIGNATURE-----
Comment: Using GnuPG with Thunderbird - https://www.enigmail.net/
iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAlwySWYACgkQHPApP6U8
pFhHsBAAqemJdrmVnudsINKmxoDQuY7vz2Zo5JWNrnaUJDM08A4MGGKCka5D0RNT
Fd9LIYMRU2LRPNQECupf2idXLwYkCpwvihtqAImuydnyPPxPKXrqOlGB+Dr1rb5C
YMBoPUVhohFiT7BrSal5aNw0X9OvRh5KxhK3tPUuFKmTuF0EWT9sxYPWr0EQq3tN
OgN8fkRYcrU0Hst2I72ANpeCRnxcIdDFpxDrvRtucxlboJCE3BU4UmqXw8bOqz0G
gNowHnRKgZ1Yn/OasNGDFypDsiucIyFyR53zbVuBFFSxj+hPOtbozxzSTBdqjNPX
sfQ48d5hzRLcktYJ86ROaEor039xnMXnFr/IvkNiWHrBdnszzM9CpGzos/FINWIw
RGszmyBop+Vttt0ofmR3cjxjP53Ap4JVUv3YNTDrUDPCswcGgGM8SbG8lcSVh3wc
0CEgWenfZuzQQQGQCVdygdaa3r1I2QAzF7OAUSzMmQUHwa4J1rufaI71/eInWhJW
svLc8cOltCdTcPuEUCcM5Mr33XG3WsL4lmWJmCvq009jewLzoru+sj9Q5SLPcX8N
Bpb/gGycyby/Ox/XC8Qez+mOMZ5Gt+CdKBeNW7PXoPqdj6E9zzO9TUavfkUHtdMl
DgdGnAkFIGZx3gVIOznz/v3A0PGvx1ukMzgTPq9gOb5+UQvqN9E=
=i5Oy
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: buildbot failure in on tomcat-85-trunk
Posted by Rainer Jung <ra...@kippdata.de>.
Hi Chris,
Am 05.01.2019 um 22:25 schrieb Christopher Schultz:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> All,
>
> Hmm... this my fault. The EncryptInterceptor tests pass on my local
> machine but not on the buildbot server, apparently.
>
> How can I get the log file from the test failure? junit's stdout isn't
> enough.
Not the answer to your question, but the test fails for me as well - if
I run them using Java 7. For 8 they run fine.
Errors with Java 7 (same errors for all three connectors, I get the
errors on Solaris and eg. on RHEL 7 using Oracle HotSpot JDK 1.7.80):
Testsuite:
org.apache.catalina.tribes.group.interceptors.TestEncryptInterceptor
Tests run: 18, Failures: 0, Errors: 3, Skipped: 2, Time elapsed: 2.375 sec
------------- Standard Error -----------------
06-Jan-2019 15:20:11.215 SEVERE [main]
org.apache.catalina.tribes.group.interceptors.EncryptInterceptor.sendMessage
Failed to encrypt message
06-Jan-2019 15:20:11.252 SEVERE [main]
org.apache.catalina.tribes.group.interceptors.EncryptInterceptor.sendMessage
Failed to encrypt message
File message.bin does not exist. Skipping test.
------------- ---------------- ---------------
Testcase: test192BitKey took 1.281 sec
Caused an ERROR
java.security.InvalidKeyException: Illegal key size; No faulty members
identified.
org.apache.catalina.tribes.ChannelException:
java.security.InvalidKeyException: Illegal key size; No faulty members
identified.
at
org.apache.catalina.tribes.group.interceptors.EncryptInterceptor.sendMessage(EncryptInterceptor.java:130)
at
org.apache.catalina.tribes.group.interceptors.TestEncryptInterceptor.roundTrip(TestEncryptInterceptor.java:221)
at
org.apache.catalina.tribes.group.interceptors.TestEncryptInterceptor.roundTrip(TestEncryptInterceptor.java:210)
at
org.apache.catalina.tribes.group.interceptors.TestEncryptInterceptor.test192BitKey(TestEncryptInterceptor.java:185)
Caused by: java.security.InvalidKeyException: Illegal key size
at javax.crypto.Cipher.checkCryptoPerm(Cipher.java:1029)
at javax.crypto.Cipher.init(Cipher.java:1371)
at javax.crypto.Cipher.init(Cipher.java:1308)
at
org.apache.catalina.tribes.group.interceptors.EncryptInterceptor$BaseEncryptionManager.encrypt(EncryptInterceptor.java:499)
at
org.apache.catalina.tribes.group.interceptors.EncryptInterceptor$BaseEncryptionManager.access$000(EncryptInterceptor.java:359)
at
org.apache.catalina.tribes.group.interceptors.EncryptInterceptor.sendMessage(EncryptInterceptor.java:117)
Testcase: test256BitKey took 0.003 sec
Caused an ERROR
java.security.InvalidKeyException: Illegal key size; No faulty members
identified.
org.apache.catalina.tribes.ChannelException:
java.security.InvalidKeyException: Illegal key size; No faulty members
identified.
at
org.apache.catalina.tribes.group.interceptors.EncryptInterceptor.sendMessage(EncryptInterceptor.java:130)
at
org.apache.catalina.tribes.group.interceptors.TestEncryptInterceptor.roundTrip(TestEncryptInterceptor.java:221)
at
org.apache.catalina.tribes.group.interceptors.TestEncryptInterceptor.roundTrip(TestEncryptInterceptor.java:210)
at
org.apache.catalina.tribes.group.interceptors.TestEncryptInterceptor.test256BitKey(TestEncryptInterceptor.java:199)
Caused by: java.security.InvalidKeyException: Illegal key size
at javax.crypto.Cipher.checkCryptoPerm(Cipher.java:1029)
at javax.crypto.Cipher.init(Cipher.java:1371)
at javax.crypto.Cipher.init(Cipher.java:1308)
at
org.apache.catalina.tribes.group.interceptors.EncryptInterceptor$BaseEncryptionManager.encrypt(EncryptInterceptor.java:499)
at
org.apache.catalina.tribes.group.interceptors.EncryptInterceptor$BaseEncryptionManager.access$000(EncryptInterceptor.java:359)
at
org.apache.catalina.tribes.group.interceptors.EncryptInterceptor.sendMessage(EncryptInterceptor.java:117)
...
Testcase: testGCM took 0.007 sec
Caused an ERROR
Failed to initialize EncryptInterceptor; No faulty members identified.
org.apache.catalina.tribes.ChannelException: Failed to initialize
EncryptInterceptor; No faulty members identified.
at
org.apache.catalina.tribes.group.interceptors.EncryptInterceptor.start(EncryptInterceptor.java:84)
at
org.apache.catalina.tribes.group.interceptors.TestEncryptInterceptor.testGCM(TestEncryptInterceptor.java:272)
Caused by: java.security.NoSuchAlgorithmException: Cannot find any
provider supporting AES/GCM/PKCS5Padding
at javax.crypto.Cipher.getInstance(Cipher.java:529)
at
org.apache.catalina.tribes.group.interceptors.EncryptInterceptor$BaseEncryptionManager.createCipher(EncryptInterceptor.java:440)
at
org.apache.catalina.tribes.group.interceptors.EncryptInterceptor$BaseEncryptionManager.<init>(EncryptInterceptor.java:400)
at
org.apache.catalina.tribes.group.interceptors.EncryptInterceptor$GCMEncryptionManager.<init>(EncryptInterceptor.java:589)
at
org.apache.catalina.tribes.group.interceptors.EncryptInterceptor.createEncryptionManager(EncryptInterceptor.java:345)
at
org.apache.catalina.tribes.group.interceptors.EncryptInterceptor.start(EncryptInterceptor.java:80)
Caused by: java.security.NoSuchAlgorithmException: Unsupported mode GCM
at sun.security.pkcs11.P11Cipher.engineSetMode(P11Cipher.java:202)
at javax.crypto.Cipher$Transform.setModePadding(Cipher.java:362)
at javax.crypto.Cipher.getInstance(Cipher.java:522)
...
The first two errors can be fixed by installing the "Java Cryptography
Extension (JCE) Unlimited Strength Jurisdiction Policy Files" for Java
7. The third one is probably due to the use of an algorithm that's
simply not available for the latest free Java 7.
Probably the build slave observed the same problem(s).
Regards,
Rainer
> On 1/5/19 16:14, buildbot@apache.org wrote:
>> The Buildbot has detected a new failure on builder tomcat-85-trunk
>> while building . Full details are available at:
>> https://ci.apache.org/builders/tomcat-85-trunk/builds/1594
>>
>> Buildbot URL: https://ci.apache.org/
>>
>> Buildslave for this Build: silvanus_ubuntu
>>
>> Build Reason: The AnyBranchScheduler scheduler named
>> 'on-tomcat-85-commit' triggered this build Build Source Stamp:
>> [branch tomcat/tc8.5.x/trunk] 1850509 Blamelist: schultz
>>
>> BUILD FAILED: failed compile_1
>>
>> Sincerely, -The Buildbot
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org