Hijk Tests Hang for Days

[theory]

Since the v0.28 release, our RPM building job has been hanging for days at a time on the Hijk tests. Output:

- Building Hijk-0.28
2019/01/16-08:42:53 main (type Net::Server::HTTP -> MultiType -> Net::Server::PreFork) starting! pid(8435)
Resolved [*]:13796 to [::]:13796, IPv6
Not including resolved host [0.0.0.0] IPv4 because it will be handled by [::] IPv6
Binding to TCP port 13796 on host :: with IPv6
Group Not Defined.  Defaulting to EGID '1999 135 1999'
User Not Defined.  Defaulting to EUID '489'
2019/01/16-08:42:55 Server closing!
HTTP::Server::PSGI: Accepting connections at http://0:14492/
    # Connecting to a wrong port: 14492
    # Dying message: Connection refused at /home/jenkins-slave/workspace/CentOS6-Perl-5.20/BUILD/Hijk-0.28/blib/lib/Hijk.pm line 289.
127.0.0.1 - - [16/Jan/2019:08:43:10 -0800] "GET /?t=5 HTTP/1.1" 200 32 "-" "-"
127.0.0.1 - - [16/Jan/2019:08:43:15 -0800] "GET /?t=5 HTTP/1.1" 200 33 "-" "-"

And it's just stopped there, hanging out, nothing happening. I was unable to replicate when building manually; could there be something waiting on a TTL or something?

[gugod]

In the early days of this project we encountered a similar situation with a destination IP that is routable but not reachable. This is from t/live-connect-timeout.t, iirc. When this test was running with a physical machine, it quickly finised, but when it was running a KVM, it got stucked and the implementation of "timeout" didn't work. Eventually that was sorted out with this commit: 7439c92

I wonder if we are seeing something similar... However, if this problem is particlar to 0.28 I'm puzzled. Since that release was mostly tweaking some stuff for CPAN packaing.

That output is coming from a HTTP server launched in t/plack.t, which should respond two times, and it did -- that said, this test was tweaked in 0.28 release -- which is probably enough to be considered as a suspect. Perhaps try removing this test file and see if it still blocks your RPM packaing process.

[theory]

It's possible I simply worked around the issue in the past, or we built it on a physical machine and pushed it to our Yum repo. I don't recall that, though. At any rate, it does seem to work fine when I run it myself on a physical machine, but our VM-based Jenkins environment just chokes and hangs. I'll tweak it to delete the test tomorrow and see what happens.

[theory]

Yep, iovation/rpmcpan@d49b2de eliminated the blocking.