Skip to content
This repository has been archived by the owner on Nov 6, 2020. It is now read-only.

Error: 'json_tests::chain::block_tests::BlockchainTests_GeneralStateTest_stCallCodes' has overflowed its stack #8376

Closed
masonforest opened this issue Apr 11, 2018 · 2 comments · Fixed by #8439
Labels
F4-tests 💻 Tests need fixing, improving or augmenting. Z1-question 🙋‍♀️ Issue is a question. Closer should answer.

Comments

@masonforest
Copy link

Hello 👋

Thanks for building Parity!

I’m getting a stack overflow when running the JSON tests on master.

Parity version Latest master (0a170efa)
Operating system macOS High Sierra 10.13.3
Installed from source

Steps to reproduce

$ git clone --recursive https://github.com/paritytech/parity
$ cd parity/ethcore/src/json_tests
$ cargo test --features json-tests
…
thread 'json_tests::chain::block_tests::BlockchainTests_GeneralStateTest_stCallCodes' has overflowed its stack
fatal runtime error: stack overflow
error: process didn't exit successfully: `/Users/masonf/tmp/parity/target/debug/deps/ethcore-2362ef09be4afd18` (signal: 6, SIGABRT: process abort signal)

Full output: https://gist.github.com/masonforest/bbc887a50ffa75c86396bf244e6297af

Let me know if there's any other info I can provide that would be helpful.

@sorpaas
Copy link
Collaborator

sorpaas commented Apr 19, 2018

Looks like this passes on release build cargo test --features json-tests --release -- BlockchainTests_GeneralStateTest_stCallCodes but would stack overflow on debug build cargo test --features json-tests -- BlockchainTests_GeneralStateTest_stCallCodes.

@tomusdrw tomusdrw added the Z1-question 🙋‍♀️ Issue is a question. Closer should answer. label Apr 19, 2018
@tomusdrw
Copy link
Collaborator

tomusdrw commented Apr 19, 2018

It's a known issue, json-tests have to be run in --release mode since some of them are really pushing the interpreter to the limits (deeply nested calls).

@5chdn 5chdn added this to the 1.11 milestone Apr 24, 2018
@5chdn 5chdn added the F4-tests 💻 Tests need fixing, improving or augmenting. label Apr 24, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
F4-tests 💻 Tests need fixing, improving or augmenting. Z1-question 🙋‍♀️ Issue is a question. Closer should answer.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants