Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

req test suite failure re: httpbin.org/status/102 (InvalidStatusLine "0") #44

Closed
DanBurton opened this issue May 7, 2018 · 1 comment
Milestone

Comments

@DanBurton
Copy link

Failures:

  httpbin-tests/Network/HTTP/ReqSpec.hs:370:
  1) Network.HTTP.Req, receiving status code 102, works
       uncaught exception: HttpException (VanillaHttpException (HttpExceptionRequest Request {
         host                 = "httpbin.org"
         port                 = 443
         secure               = True
         requestHeaders       = []
         path                 = "/status/102"
         queryString          = ""
         method               = "GET"
         proxy                = Nothing
         rawBody              = False
         redirectCount        = 10
         responseTimeout      = ResponseTimeoutDefault
         requestVersion       = HTTP/1.1
       }
        (InvalidStatusLine "0")))

Randomized with seed 1813816718

I was able to reproduce this locally like so:

stack unpack req-1.0.0 && cd req-1.0.0
echo 'resolver: lts-11.7' > stack.yaml
stack build --haddock --test --bench --no-run-benchmarks

I'm guessing this is just httpbin changing things, so I will simply mark the test suite as an expected failure in stackage until this is addressed.

DanBurton added a commit to commercialhaskell/stackage that referenced this issue May 7, 2018
@mrkkrp
Copy link
Owner

mrkkrp commented May 8, 2018

I think this has been addressed by 60524bc. New version, 1.1.0 will be released soon.

@mrkkrp mrkkrp closed this as completed May 8, 2018
@mrkkrp mrkkrp added this to the 1.1.0 milestone May 8, 2018
DanBurton added a commit to commercialhaskell/stackage that referenced this issue May 10, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants