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
This behavior was observed on the imp-haskell test.
Steps to Reproduce
Add --color on to KPROVE_FLAGS on the test Makefile.
Expected Results
From krpove's help message:
kprove --help
Usage: kprove [options] <file>
Options:
...
--color
Use colors in output. Default is on.
Possible Values: [OFF, ON, EXTENDED]
Given that the color should be ON as default, the test shouldn't fail, but it does fail. So the actual behavior isn't aligned with the help's message. One of them should be fixed.
The use of --color shouldn't affect the order of the failing output.
The text was updated successfully, but these errors were encountered:
We can change the pretty printer in the llvm-backend to check the output w/o colors.
When we convert the collection items into a string, make sure the color flag is off. @gtrepta can you check if you can include it in runtimeverification/llvm-backend#836
It doesn't look like kprove is using the kprint command for output. I also tested the output manually with kprint and the ordering doesn't change between colors being on and off.
Instead, kprove is using the KPrint class in org.kframework.unparser. Still investigating...
What component is the issue in?
Front-End
Which command
What K Version?
v6.0.96-0-g35348949c6
Operating System
Linux
K Definitions (If Possible)
This behavior was observed on the imp-haskell test.
Steps to Reproduce
Add
--color on
toKPROVE_FLAGS
on the test Makefile.Expected Results
krpove
's help message:Given that the color should be ON as default, the test shouldn't fail, but it does fail. So the actual behavior isn't aligned with the help's message. One of them should be fixed.
--color
shouldn't affect the order of the failing output.The text was updated successfully, but these errors were encountered: