Problem: PartialOrderPlanner.execute() sometimes either 1. finds no plan: "Couldn't find a solution" 2. finds an incorrect one in which it prints beforehand "Probably Wrong"
According to this, the following code should have this output:
or just no plan at all:
Couldn't find a solution (None, None)
I can't find any pattern that would indicate why this should happen. Also, if other plans are run in the same session (with no other code run in between) sometimes they appear to randomly fail (incorrect or not found) despite the success of other plans, e.g. I have found success for spare_tire but then a fail for simple_blocks_world:
sbw = simple_blocks_world()
pop = PartialOrderPlanner(sbw)
pop.execute()
Couldn't find a solution
(None, None)
Have also tried:
checking out the original commit for this notebook 55cc39d and using python 3.7 but I get similarly inconsistent results.
If issues like this could be avoided by pinning package versions in requirements.txt or at least printing and saving the versions used in the travis ci builds, that would be nice.
Problem: PartialOrderPlanner.execute() sometimes either 1. finds no plan: "Couldn't find a solution" 2. finds an incorrect one in which it prints beforehand "Probably Wrong"
According to this, the following code should have this output:
However, sometimes when I run it (from restarted kernel, i.e. no variables), I get:
or just no plan at all:
Couldn't find a solution (None, None)
I can't find any pattern that would indicate why this should happen. Also, if other plans are run in the same session (with no other code run in between) sometimes they appear to randomly fail (incorrect or not found) despite the success of other plans, e.g. I have found success for spare_tire but then a fail for simple_blocks_world:
Have also tried:
My environment:
If issues like this could be avoided by pinning package versions in requirements.txt or at least printing and saving the versions used in the travis ci builds, that would be nice.