From my observations, sumatra does definitely store the diff (having been configured as smt configure --on-changed=store-diff) when the changes are uncommitted. However, on running smt repeat, it appears that the diff is not being applied and the output ends up not matching. I have manually checked the fact that outpu correspinding to the uncommitted changes is not present in the repeated run. This seems to be a very important issue as there is a lot of times where we cannot afford to commit every single test/analysis done on a piece of code.
From my observations, sumatra does definitely store the diff (having been configured as
smt configure --on-changed=store-diff) when the changes are uncommitted. However, on runningsmt repeat, it appears that the diff is not being applied and the output ends up not matching. I have manually checked the fact that outpu correspinding to the uncommitted changes is not present in the repeated run. This seems to be a very important issue as there is a lot of times where we cannot afford to commit every single test/analysis done on a piece of code.