Running multiple tests with trace-verbosity results in a panic

[amanusk]

Select Tool

snforge

Foundry Version

0.43.0

What operating system are you using?

Linux

What system architecture are you using?

x86

Issue Description

Running multiple tests with --trace-verbosity detailed, results in an error

Repo:
https://github.com/amanusk/starknet-foundry-template

Error:

contract name should be present in `ContractsData`
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
[ERROR] task 17 panicked with message "contract name should be present in `ContractsData`"

Renning without traces doesn't result in an error

Backtrace

thread 'tokio-runtime-worker' panicked at crates/debugging/src/trace/collect.rs:106:14:
contract name should be present in `ContractsData`
stack backtrace:
   0: rust_begin_unwind
   1: core::panicking::panic_fmt
   2: core::option::expect_failed
   3: core::ops::function::impls::<impl core::ops::function::FnOnce<A> for &mut F>::call_once
   4: <alloc::vec::Vec<T> as alloc::vec::spec_from_iter::SpecFromIter<T,I>>::from_iter
   5: debugging::trace::types::Trace::new
   6: forge_runner::test_case_summary::TestCaseSummary<forge_runner::test_case_summary::Single>::from_run_completed
   7: forge_runner::running::extract_test_case_summary
   8: forge_runner::running::run_test::{{closure}}
   9: tokio::runtime::task::core::Core<T,S>::poll
  10: tokio::runtime::task::harness::Harness<T,S>::poll
  11: tokio::runtime::blocking::pool::Inner::run
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
[ERROR] task 17 panicked with message "contract name should be present in `ContractsData`"

Command Line Output

No response