On Tue, Nov 22, 2022 at 12:18 PM Eric Sunshine <sunshine@xxxxxxxxxxxxxx> wrote: > On Tue, Nov 22, 2022 at 11:52 AM Rudy Rigot <rudy.rigot@xxxxxxxxx> wrote: > > > you might write the commit message like this > > - the end of what I get when running 'sh ./t7508-status.sh -v': > > https://gist.github.com/rudyrigot/ee80f3d59231f25698c9dd6c48d8ab85. It > > seems like 2 of my 3 tests are failing, but the output isn't very > > helpful to figure out why. > > The second 'gist' URL seems broken, so I can't comment on the exact > output. Without having seen the actual problem, I can't really provide > direct feedback for fixing the precise issue, however... Despite the URL of the second git being broken, I notice that you have some "-v" output tacked onto the first gist. Indeed, the "-v" output isn't very helpful here. What I normally do when debugging failing tests is run with "-x" and "-i". The "-x" shows all the output the test produces, including any error messages. So "./t7508-status.sh -x -i" would likely make it easier to diagnose such failures. (But first try the suggestion I made in my previous reply for isolating the new tests in their own repository.)
