Gerard Murphy comments

Results 28 comments of


                                            Gerard Murphy

trafficstars

Integration with Scalacheck.

Given #42, it may be acceptable - if somewhat hokey - to go with Scalacheck parameters for the outer loop that discovers a failure, and to supply a strategy for...

java.lang.AssertionError: assertion failed: TS[753540, 753539, 753538] attempted to take ownership of B which is already owned by committable TS[808807, 753540, 753539, 753538]

@Gedochao I'm seeing the same problem (with different integer values in the assertion failure). I've managed to minimize the reproduction down to what I think is small enough to think...

java.lang.AssertionError: assertion failed: TS[753540, 753539, 753538] attempted to take ownership of B which is already owned by committable TS[808807, 753540, 753539, 753538]

**Reproduction: ** The repository: https://github.com/sageserpent-open/kineticMerge at commit: af774510ad44a859bd28ca6b7a6549677fea9507 (branch: `dotty-typer-assertion-failure-reproduction`) contains the minimized source code and `build.sbt`. Scala build uses 3.3.4. Code follows inline: 1. `build.sbt` ```scala import scala.language.postfixOps lazy...

java.lang.AssertionError: assertion failed: TS[753540, 753539, 753538] attempted to take ownership of B which is already owned by committable TS[808807, 753540, 753539, 753538]

I should add that changing the offending ` >> StateT.pure(computedResult)` to the more pedestrian `.flatMap(_ => StateT.pure(computedResult))` avoids the bug altogether. For that matter, remembering to put in `import cats.syntax.flatMap.*`...

java.lang.AssertionError: assertion failed: TS[753540, 753539, 753538] attempted to take ownership of B which is already owned by committable TS[808807, 753540, 753539, 753538]

Removed the commit for reproduction from the Kinetic Merge repository, as apparently this is a duplicate of #23663; that has been closed.

Loss of location of assert when using smart asserts.

To provide some context, what I was trying to do was to use uTest's assertions from within a JUnit test - this is because I use a parameterised test framework...

Loss of location of assert when using smart asserts.

In the meantime, I've discovered Expecty, which as a standalone assertion library suits my purposes better. I imagine that the majority of users of uTest will be using the whole...