You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 4, 2024. It is now read-only.
With the -r / --randomize flag, riscv-ctg uses python-constraint's MinConflictsSolver. This is not reproducible. It seems like this was noticed at least:
A obvious down-side of using random solvers is the fact that the same test cannot be reproduced again. However, the typical intent of users of CTG would be to generates tests satisfying the cover-points defined in the CGF. Since that is guaranteed by CTG, the reproducibility issue can be set aside.
I guess this was really set aside because unfortunately MinConflictsSolver uses global random and doesn't let you provide a seed. This can be easily worked around by seeding the global random before solving, or by copying & fixing MinConflictsSolver. But I think I will just fix it in that project.
I also noticed some other uses of the global random in riscv-ctg which should not be there: several uses of random.choice in cross_comb.py.
The text was updated successfully, but these errors were encountered:
With the
-r
/--randomize
flag, riscv-ctg usespython-constraint
'sMinConflictsSolver
. This is not reproducible. It seems like this was noticed at least:I guess this was really set aside because unfortunately
MinConflictsSolver
uses globalrandom
and doesn't let you provide a seed. This can be easily worked around by seeding the globalrandom
before solving, or by copying & fixingMinConflictsSolver
. But I think I will just fix it in that project.I also noticed some other uses of the global
random
in riscv-ctg which should not be there: several uses ofrandom.choice
incross_comb.py
.The text was updated successfully, but these errors were encountered: