CI logs flooded with stack trace noise from #[should_panic] tests

[garious]

Problem

A quick scan of the CI logs for error messages won't tell you the real error, because the stack traces from unit-tests using #[should_panic] end up in the logs.

Proposed Solution

Find a way to not display stack traces is passing tests.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

[stale]

This stale issue has been automatically closed. Thank you for your contributions.