Update language levels, fix erlang and rust in CI#1817
Update language levels, fix erlang and rust in CI#1817jeking3 merged 3 commits intoapache:masterfrom
Conversation
|
@jeking3 Sorry for the delay. I'm trying to fix the rust tutorial build failures right now, and I'll try to fix the rust build specifically so that we use a pinned version of rustc as opposed to whatever's on stable at the time the docker container is built. |
b6c8dff to
09e3137
Compare
|
Issue reproduced locally (gotta love docker containers)... looking into it. |
|
Now the erlang feature test for TLS is breaking. See what happens when a language rots because it's not being built? |
|
So erlang 22 includes erlang ssl 9.3 which disables TLS 1.0 and 1.1 by default, but TLSv1.2 doesn't seem to be working either. I'll have to back down to erlang 21 for now unless someone with some erlang knowledge can fix the TLS feature test. |
3f67d54 to
dd10e19
Compare
|
The dlang unit test async_test is failing for ssl and hanging causing those builds to fail. This seems to be related to the newer version of dlang in use. I had upgraded from 2.083 to 2.086. I'll try to bisect it. |
|
One last thing to take care of, the Xenial Dockerfile isn't working on install of cabal. |
- Include rebar3 in docker image so erlang builds in CI - Include the correct path in docker image so rust builds in CI - Updated common lisp (sbcl) to 1.5.3 in docker image - Updated dlang to 2.087.0 in docker image - Updated dart to 2.0.0 in xenial docker image - Updated dart to 2.4.0 in bionic docker image - Updated erlang to 22.0 in docker image - Updated openjdk to 11.0.3 in docker image - Updated node.js to 10.16 in docker image - Updated rust to 1.34.0 in xenial docker image - Updated rust to 1.35.0 in bionic docker image THRIFT-4905: Disable hanging experimental dlang async ssl test
Due to the way SSL layers on top of sockets, it was possible to complete a connection and then have the server close it. This would happen if the client is not checking certificates but the server is. The TSSLSocket unit test was enhanced to do a read and a write as well as just connecting to ensure a more complete test. The TSocket read() and write() calls were leaking OSError, socker.error, and ssl.Error exceptions. These cases are now wrapped into a TTransportException of the appropriate type, and the original exception is added as an argument named inner.
The latest ssl (9.3) in erl does not support TLSv1.0 or TLSv1.1 by default and cross tests are failing. Since csharp was deprecated in favor of netstd, ignoring it.
|
The issue with the Xenial build is (hopefully) a server error on the haskell server side. As such, I'm going to merge this. |
Uh oh!
There was an error while loading. Please reload this page.