Skip to content

Conversation

avsej
Copy link
Contributor

@avsej avsej commented Dec 30, 2017

After the change, when stacktraces rendered in reversed order (most recent
call first), this method removed all stacktraces in the test failures.

After the change, when stacktraces rendered in reversed order (most recent
call first), this method removed all stacktraces in the test failures.
@dom96
Copy link
Contributor

dom96 commented Dec 30, 2017

After the change, when stacktraces rendered in reversed order (most recent
call first)

Was this changed in Nim? Are stack traces rendered this way now?

@avsej
Copy link
Contributor Author

avsej commented Dec 30, 2017

I meant, that in the past this code used to find beginning of stacktrace, and copied it into output buffer, but now, when stacktraces go in reversed order, it cannot find the marker substrings, and just return empty buffer. "After the change..." means "After the changing stacktrace rendering", and it already in devel.

@Araq Araq merged commit 3f2636c into nim-lang:devel Dec 31, 2017
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

Successfully merging this pull request may close these issues.

3 participants