That assertion is of course intended to catch an internal software
inconsistency and not be a "user error", but it is related to ensuring that
the value of a property being assigned to a subcase is indeed one of the
values defined for the case.
This of course "can't happen", but somehow it has... :-)
If you are generating a value could you try to just insert the actual
value to see if that changes anything?
On 2/9/21 8:46 AM, Dominic Walters via discuss wrote:
> Hi,
>
> I'm trying to build a test for a HDL Worker and I keep hitting a failed
> assertion check in tools/ocpigen/src/tests.cxx.
>
> The check is done on line 1383 of tools/ocpigen/src/tests.cxx ·
> release-2.0.1 · OpenCPI / OpenCPI · GitLab
> <https://gitlab.com/opencpi/opencpi/-/blob/release-2.0.1/tools/ocpigen/src/tests.cxx>
> .
>
> Any suggestions as to what I'm doing wrong? I can't really tell what
> "attrs" is doing in that code.
> To my knowledge:
> * I have set every property of the worker (either by using the default of
> a parameter, by defining "value", or by defining "generate"). In cases.txt
> every property has a value or a file it is generated in.
> * I am generating input for every port.
> * The worker is built for my simulation platform.
>
> I have had this check fail in the past, but unfortunately I can't remember
> how I fixed/avoided it.
>
> Thanks.
>
Received on Tue Feb 09 2021 - 14:00:45 CST