Open schrum2 opened 2 years ago
This error as well:
testVerifyConsistency(edu.southwestern.tasks.gvgai.zelda.study.DungeonNoveltyTest): Unable to place new node : QMGV
Once again, fairly rare, but still annoying
I've disabled this test. It passes most of the time, but when it messes up a Maven build it is really annoying. Still, should find out what the root cause is. Seems to be the choice of randomly generated string codes for the rooms, but shouldn't this be pseudo random in a deterministic way? Maybe simply resetting the seed at the start of the test could solve the issue.
Specific error in Maven build is
testVerifyConsistencyAcrossRepresentations(edu.southwestern.tasks.gvgai.zelda.study.DungeonNoveltyTest): Unable to place new node : YVUT
It is reasonably rare, but not rare enough.