Closed finndfr closed 1 year ago
Thanks for your helpful description of this problem. Yes, it is a Tcases defect. A fix is coming soon.
Here's what's happening. Per standard procedure, Tcases generates a failure case with an array value larger than maxItems
. But that can't be done without violating the uniqueItems
condition. Hence the "Unable to resolve" error.
The first problem is that this error should just skip the test case and proceed, not bring the whole program to a halt. The next problem is that the message offers no explanation for what went wrong. But the root problem is that the infeasibility of this case should have been recognized earlier -- no such failure should have been generated at all.
Thanks for the quick reply. My real input is an unbounded list of enum strings, with an enum cardinality of 4. But I added both the uniqueItems
and maxItems
constraint to try to make things simpler. As a workaround I've had a bit more luck modeling this as 4 booleans such as contains_banana
, assuming duplicates are dealt with.
Fixed in release 4.0.2
I am hitting the following error when trying to create an input type that is an array of enums. I actually have this structure in my input several times, but I'm still having the same error with this reduced example. Maybe this is a bug? Or maybe I'm missing something in my definition?
My simplified input file is as follows. I am invoking with a plain
tcases <project>
.My log: