Open lucaskanashiro opened 3 years ago
/cc: @makeable, @stakach: could you perhaps take a look at this?
I don't expect a different behavior on s390x architecture, for example, HttpParser::Instance#initialize #type should indeed default to :both
and probably not :request
. Likewise, I don't understand why it'd return false
if the "Upgrade header" is already set.
For other architectures, this works fine, maybe we're missing something on s390x? or is there something wrong with tests in general sense, maybe(!?), 'cause I don't see an obvious reason for them to fail here?
Thanks in advance! 🙈
Oh well, I hope the problem isn't due to native extensions on s390x. I've seen sometimes those to be a problem, but hoping this wouldn't be it here as well (or is it!?) 🙈
The following tests are failing in Debian and Ubuntu infrastructure on s390x architecture:
Full logs:
https://buildd.debian.org/status/fetch.php?pkg=ruby-http-parser&arch=s390x&ver=1.2.1-4&stamp=1604434045&raw=0 https://launchpadlibrarian.net/526217639/buildlog_ubuntu-hirsute-s390x.ruby-http-parser_1.2.1-4_BUILDING.txt.gz
FWIW I ran the tests from the current
master
branch in a s390x VM and I got the same failures.