
I am trying to run raco in a docker container based on fedora:26 and I keep getting: SSL_library_init: implementation not found; no arguments provided

Which dep am I missing here? I am installing openssl and openssl-devel which I thought was the requirement.

ah.. .the missing dep was openssl-libs. :slightly_smiling_face:

@mflatt you can see a more verbose file test output here: https://travis-ci.org/racket/racket/builds/299648951

they all seem to hang in the same place

Looks like they’re hanging at an IPv6 test

line 1528 of “file.rktl”

this suggests that maybe we shouldn’t expect that to work: https://github.com/travis-ci/travis-ci/issues/3302#issuecomment-159748795

The test is set up to accommodate environments where IPv6 is not supported so that listening at "::1" or connecting to "::1" raises an exception. Maybe something has gone wrong in error handling for that case. (If trying to use "::1" fails without reporting an error, then I don’t know offhand how to accommodate that.)

@mflatt is there an expression I could try to run that would tell us the difference?

It might be interesting to know whether (listen "::1")
by itself hangs, but I think it will take more work to track down the problem

@mflatt what’s the listen
function you refer to? tcp-listen
doesn’t seem like the right thing there

Oh, I see… I did mean tcp-listen
, but I see that tcp-listen
in the test doesn’t have a hostname. I wonder if adding the hostname to tcp-listen
would help. (I think it would still be a valid test.)

I’m still confused — what does "::1" mean then?

::1 looks like an ipv6 address

right, it is

(sorry, should have read up)

but I’m confused about what mflatt means to try with tcp-listen

as the 4th argument

That is, I orginally had in mind (tcp-listen 0 5 #t "::1")

@lancellotti.net has joined the channel

Btw I made some docker images for Racket that you might be able to use instead. I’m curious how you’re planning on using Racket and docker together

@samth I’m planning on merging the linux-natipkg docker build PR later tonight unless you’ve got objections

@notjack I think my thoughts here are less useful than yours anyway ;)

@samth ack ;)

@samth oh, could you enable Travis on that repo? There’s a docker service available to travis runs so I want to try and get the installer tests running on that

Done

Fantastic, thanks

@mflatt that tcp-listen
test failed: https://travis-ci.org/racket/racket/jobs/299991848#L1661