The case of the missing stack trace

20 views
Skip to first unread message

Øyvind Harboe

unread,
Jan 27, 2022, 6:39:43 AMJan 27
to chisel-users
Silly question: How do I run tests with "--full-stacktrace" ? 



sbt "test:testOnly ..."
[deleted]
[info]   chisel3.internal.ErrorLog$$anon$1: Fatal errors during hardware elaboration. Look above for error list.
[info]   at ... ()
[info]   at ... ()
[info]   at ... (Stack trace trimmed to user code only. Rerun with --full-stacktrace to see the full stack trace)


Øyvind Harboe

unread,
Jan 27, 2022, 7:22:54 AMJan 27
to chisel-users
Shot in the dark... I wasn't able to try it locally, see separate post on publishLocal instructions.


Adding PrintFullStackTraceAnnotation change anything.

Jack Koenig

unread,
Jan 27, 2022, 2:17:54 PMJan 27
to chisel...@googlegroups.com
This is a fantastic question, I've opened a PR to chiseltest to add instructions for this specifically: https://github.com/ucb-bar/chiseltest/pull/501

--
You received this message because you are subscribed to the Google Groups "chisel-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chisel-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/chisel-users/e771d39d-95b5-42cf-b4ec-87171e429432n%40googlegroups.com.
Reply all
Reply to author
Forward
0 new messages