Test validation of cyclic graph + local consts, doc failures #224
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
test_cyclic
creates a cyclic DFG, and this validates :-(. We don't have anything in validation to look for this.test_local_const
creates a graph with a LoadConstant node that is not in the causal cone of the Input. This passes validation, because the DfsPostOrder used invalidate_children_dag
currently traverses both ways along edges :-(, I think validation should fail here, and that the fix is in portgraph.test_local_const
then goes on to add the missing edge, and that still passes, but if we fixed the traversal to only go forwards,validate_children_dag
would then fail as it wouldn't have visited the Const node (but would count it in the children); we'd then need the fix detailed insidevalidate_children_dag
I'd love to turn these into "expected-fail" tests but that looks quite hard, best plan appears to be to use cargo-nextest