The wt tool often gets broken as a result of internal changes to the WiredTiger library.

It's difficult to detect these regressions since you have to check manually in cases where you suspect your change might interfere with the tool. What usually ends up happening is that whenever you try to use the tool, you need to spend some time debugging it.

It'd be better if we had some more tests around the tool to ensure that it's always dumping, verifying, etc the right data. It's also important for correctness in WiredTiger because we use the tool in a few of our tests to verify that our data files are in a good state.