-
-
Notifications
You must be signed in to change notification settings - Fork 74
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
Test failure: "key \"evidence_due_by\" not present" #96
Comments
I started work on this but couldn't figure out how to run the tests. @dmjio any advice? [ben@lithium:~/src/stripe]$ nix-shell default.nix --attr stripe-haskell
these paths will be fetched (0.01 MiB download, 0.03 MiB unpacked):
.....
[nix-shell:~/src/stripe]$ stack test
stripe-http-streams-2.3.0: test (suite: tests)
stripe-http-streams-2.3.0: Test suite tests failed
Log files have been written to: /home/ben/src/stripe/.stack-work/logs/
Test suite failure for package stripe-http-streams-2.3.0
tests: exited with: ExitFailure 1
Full log available at /home/ben/src/stripe/.stack-work/logs/stripe-http-streams-2.3.0-test.log
Please enter your Stripe *TEST* account
tests: <stdin>: hGetLine: end of file
[nix-shell:~/src/stripe]$ |
First step would be to get into a shell for stripe-http-streams (stripe-tests is used in the test suite of stripe-http-streams). Next step would be to ensure dependencies are all correct (contingent on your nixpkgs version). Bump the upper bounds if need be. Then once you can cabal configure —enable-tests, run “cabal test” in that shell.
…Sent from my iPhone
On May 11, 2018, at 5:19 PM, Ben Sima ***@***.***> wrote:
I started work on this but couldn't figure out how to run the tests. @dmjio any advice?
***@***.***:~/src/stripe]$ nix-shell default.nix --attr stripe-haskell
these paths will be fetched (0.01 MiB download, 0.03 MiB unpacked):
.....
[nix-shell:~/src/stripe]$ stack test
stripe-http-streams-2.3.0: test (suite: tests)
stripe-http-streams-2.3.0: Test suite tests failed
Log files have been written to: /home/ben/src/stripe/.stack-work/logs/
Test suite failure for package stripe-http-streams-2.3.0
tests: exited with: ExitFailure 1
Full log available at /home/ben/src/stripe/.stack-work/logs/stripe-http-streams-2.3.0-test.log
Please enter your Stripe *TEST* account
tests: <stdin>: hGetLine: end of file
[nix-shell:~/src/stripe]$
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Okay, I think it's working, thanks for the help. I'll write up a
CONTRIBUTING.md with this info to try and help newcomers.
David Johnson <notifications@github.com> writes:
… First step would be to get into a shell for stripe-http-streams (stripe-tests is used in the test suite of stripe-http-streams). Next step
would be to ensure dependencies are all correct (contingent on your nixpkgs version). Bump the upper bounds if need be. Then
once you can cabal configure —enable-tests, run “cabal test” in that shell.
Sent from my iPhone
> On May 11, 2018, at 5:19 PM, Ben Sima ***@***.***> wrote:
>
> I started work on this but couldn't figure out how to run the tests. @dmjio any advice?
>
> ***@***.***:~/src/stripe]$ nix-shell default.nix --attr stripe-haskell
> these paths will be fetched (0.01 MiB download, 0.03 MiB unpacked):
> .....
> [nix-shell:~/src/stripe]$ stack test
> stripe-http-streams-2.3.0: test (suite: tests)
> stripe-http-streams-2.3.0: Test suite tests failed
> Log files have been written to: /home/ben/src/stripe/.stack-work/logs/
> Test suite failure for package stripe-http-streams-2.3.0
> tests: exited with: ExitFailure 1
> Full log available at /home/ben/src/stripe/.stack-work/logs/stripe-http-streams-2.3.0-test.log
>
>
> Please enter your Stripe *TEST* account
> tests: <stdin>: hGetLine: end of file
>
>
> [nix-shell:~/src/stripe]$
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub, or mute the thread.
>
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.
|
bsima
added a commit
to bsima/stripe
that referenced
this issue
May 12, 2018
This is just a really basic document from the info you gave me, but it's a start. dmjio#96 (comment)
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Stripe's changelog indicates that
evidence_due_by
was replaced byevidence_details
in 2014.The text was updated successfully, but these errors were encountered: