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
I'm working on tests that rely on proper_fsm. I'm noticing that proper_fsm:commands(?MODULE) generates truly gigantic command sequences. I'm using a lot of inferred state, i.e. delayed symbolic evaluations to effect state and it seems that sometimes these things becoming recursive. With that I mean code like this, that uses symbolic functions to calculate state:
This code works fine for shorter sequences, but the generator produces gigantic examples, that literally causes my beam VM to run out of memory.
So is there a way to limit the size of these things?
Here is a (bigger) example. There is nothing wrong with this test case, it does what it's supposed to. The issue is that the generator produces much, much bigger ones.
Hi there,
I'm working on tests that rely on
proper_fsm
. I'm noticing thatproper_fsm:commands(?MODULE)
generates truly gigantic command sequences. I'm using a lot of inferred state, i.e. delayed symbolic evaluations to effect state and it seems that sometimes these things becoming recursive. With that I mean code like this, that uses symbolic functions to calculate state:Some of the more extreme examples (That don't blow up):
If I sample a few of the outputs, you'll see the delayed evaluation calls:
This code works fine for shorter sequences, but the generator produces gigantic examples, that literally causes my beam VM to run out of memory.
So is there a way to limit the size of these things?
Here is a (bigger) example. There is nothing wrong with this test case, it does what it's supposed to. The issue is that the generator produces much, much bigger ones.
Thanks!
R
The text was updated successfully, but these errors were encountered: