Failed assertions in Scala 3 produce unhelpful stack traces

[malcolmredheron]

I'm confused by the stack traces that I get when a utest assertion fails in scala 3. Specifically, the only line in the trace that refers to the test file seems to point to the line with Tests { on it, not the line of the assertion

I forked the utest repo and changed an assertion to fail. Here's how to reproduce it:

• Clone https://github.com/malcolmredheron/utest-confusing-assertion/tree/broken-assertion
• Run ./mill utest.jvm[3.3.3].test.testOnly "*HelloTests*"
• For me, this produces:

[113/113] utest.jvm[3.3.3].test.testOnly
[113] Setting up CustomFramework
[113] -------------------------------- Running Tests --------------------------------
[113] + test.utest.examples.HelloTests.test1 6ms  
[113] + test.utest.examples.HelloTests.test2.inner 0ms  1
[113] + test.utest.examples.HelloTests.test3 0ms  
[113] X test.utest.examples.HelloTests.test4 3ms 
[113]   utest.AssertionError: 1 == 2
[113]     utest.asserts.Asserts$.assertImpl(Asserts.scala:30)
[113]     test.utest.examples.HelloTests$.$init$$$anonfun$1$$anonfun$4(HelloTests.scala:5)
[113] Tearing down CustomFramework
[113] Tests: 4, Passed: 3, Failed: 1
[113/113] =================================================== utest.jvm[3.3.3].test.testOnly *HelloTests* ====================================================== 1s
1 tasks failed
utest.jvm[3.3.3].test.testOnly 1 tests failed: 
  test.utest.examples.HelloTests test.utest.examples.HelloTests.test4

• By contrast, ./mill utest.jvm[2.13.14].test.testOnly "*HelloTests*" mentions line 21 instead of line 5