tests: assert by compute test fails (due to unexpected json from VIR interpreter)

[bsdinis]

On main as of today (i have anecdotally been seeing this for a while now) running the test suite fails on examples_assert_by_compute

$ vargo build && vargo nextest run -p rust_verify_test --
[...]
        FAIL [  13.455s] rust_verify_test::examples examples_assert_by_compute
──── STDOUT:             rust_verify_test::examples examples_assert_by_compute

running 1 test
test examples_assert_by_compute ... FAILED

failures:

failures:
    examples_assert_by_compute

test result: FAILED. 0 passed; 1 failed; 0 ignored; 0 measured; 135 filtered out; finished in 13.41s

──── STDERR:             rust_verify_test::examples examples_assert_by_compute
[unexpected json] "note: assert_by_compute has been running for 2 seconds (depth: 123, iterations: 23225)"
[unexpected json] "note: assert_by_compute has been running for 2 seconds (depth: 288, iterations: 24068)"
[unexpected json] "note: assert_by_compute has been running for 4 seconds (depth: 144, iterations: 49051)"
- example rust_verify/../../examples/assert_by_compute.rs - mode: ExpectSuccess - failed -

- stdout -
verification results:: 31 verified, 0 errors



thread 'examples_assert_by_compute' panicked at rust_verify_test/tests/examples.rs:158:9:
assertion failed: false
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
[...]

Looking over the code, it seems that the [unexpected json] lines are printed by the parse_diags because the VIR interpreter is issuing a slow warning.

This does not seem major but definitely is causing me some testing/CI problems.