If you have an invalid commit anywhere in the dependency tree, it can be hard to find especially because it can come from an arbitrary commit of any of the repos. Since manifests are read via git commands, this allows us to easily log every single manifest so we can simply search for the bad commit and trace backwards in the logging output to determine the cause.
fyi @daveparry this is how I debugged the bad sifive-blocks commit, thus once 0.12 is out you should be able to just do wit -vvvv ... and it will log everything you need to know to debug such issues.
If you have an invalid commit anywhere in the dependency tree, it can be hard to find especially because it can come from an arbitrary commit of any of the repos. Since manifests are read via git commands, this allows us to easily log every single manifest so we can simply search for the bad commit and trace backwards in the logging output to determine the cause.
fyi @daveparry this is how I debugged the bad sifive-blocks commit, thus once 0.12 is out you should be able to just do
wit -vvvv ...and it will log everything you need to know to debug such issues.