This message was deleted.
# plugin-development
s
This message was deleted.
c
It seems like something doesn’t like `@{upstream}`…
Have walked through the TestKit execution with a debugger - at the time it eventually hits ProcessBuilder (via ExecOps or directly) the args are correct.
v
Set a breakpoint the pauses the test when the command would be executed, then investigate the Git repo on the command line. Maybe the current branch does not have an upstream branch configured?
c
yea. deep into that. It isn’t TestKit, it a bad test-generated Git repo combined with challenging error messages from Git. You are correct - the upstream is misconfigured.