Closed kevpar closed 5 years ago
So prior to this change the method names where //something
?
@crosbymichael Yeah, the names were generated with a double "//" at the start. Maybe this was meant to use strings.Join
instead of path.Join
originally.
Have you testing this for backwards compat? A shim compiled with the existing ttrpc and a daemon with this new ttrpc?
It looks like this value is only used in interceptors, so I don't think there is any compat burden. Are there any interceptors already written that I should check? I'm not aware of any.
I don't think so, it should be good then
$ go test -race -v ./...
No output has been received in the last 10m0s, this potentially indicates a stalled build or something wrong with the build itself.
Check the details on how to adjust your build configuration on: https://docs.travis-ci.com/user/common-build-problems/#build-times-out-because-no-output-was-received
The build has been terminated
The build appears to have timed out. Is there a way to rerun it?
@dmcgowan - This failure is no way related to this change. Can we restart the tests?
I am running again but seems stuck again
My guess is the lack of vendoring is causing some issue
@dmcgowan Is there anything else you need from me here? I don't think anything in this PR could be causing the CI failure.
LGTM
Tested this locally, i'll look into the travis issues today. Looks vndr related
Signed-off-by: Kevin Parsons kevpar@microsoft.com