As of today, OpenSSL does not install via Panda

[Xliff]

Output from Panda:

==> Installing OpenSSL from a local directory '.'
==> Fetching OpenSSL
==> Building OpenSSL
==> Testing OpenSSL
t/01-basic.t ........... ok
t/02-socket.t .......... ok
t/03-rsa.t ............. ok
t/04-crypt.t ........... ok
t/05-digest.t .......... ok
t/06-digest-md5.t ...... ok
t/10-client-ca-file.t .. ok
# Failed test 'connect success'
# at t/15-issue-36.t line 15
# expected: '1'
#      got: '-1'
# Failed test 'and got some data back'
# at t/15-issue-36.t line 17
# Looks like you failed 2 tests of 4
t/15-issue-36.t ........
Dubious, test returned 2 (wstat 512, 0x200)
Failed 2/4 subtests

Test Summary Report
-------------------
t/15-issue-36.t      (Wstat: 512 Tests: 4 Failed: 2)
  Failed tests:  2, 4
  Non-zero exit status: 2
Files=8, Tests=49, 18 wallclock secs ( 0.04 usr  0.01 sys + 20.02 cusr  3.58 csys = 23.65 CPU)
Result: FAIL
The spawned command 'prove' exited unsuccessfully (exit code: 1)
  in any  at /home/cbwood/.rakudobrew/moar-nom/install/share/perl6/site/precomp/977748E31695A63ED28E91D3B1B2E9043D834ABE.1506334490.68902/58/582CB7486602954A4601BDCE5A0EAC54B05DA58A line 1
  in block  at /home/cbwood/.rakudobrew/moar-nom/install/share/perl6/site/resources/E0D978079BB5081DE986D058BB8AB08252F05CC8 line 23
  in sub MAIN at /home/cbwood/.rakudobrew/moar-nom/install/share/perl6/site/resources/E0D978079BB5081DE986D058BB8AB08252F05CC8 line 20
  in block <unit> at /home/cbwood/.rakudobrew/moar-nom/install/share/perl6/site/resources/E0D978079BB5081DE986D058BB8AB08252F05CC8 line 166
  in sub MAIN at /home/cbwood/.rakudobrew/bin/../moar-nom/install/share/perl6/site/bin/panda line 2
  in block <unit> at /home/cbwood/.rakudobrew/bin/../moar-nom/install/share/perl6/site/bin/panda line 2

And I am running the following version of rakudo:

This is Rakudo version 2017.09-86-g3f0f32146 built on MoarVM version 2017.09.1-32-g9749b0fa1
implementing Perl 6.c.

Thanks.

[Xliff]

It looks like the URL https://api.soundcloud.com/ is returning a 401 at this time, which kills this test. Does anyone else have a better test case that exposes this issue?