Skip to content

Conversation

yurishkuro
Copy link
Member

@yurishkuro yurishkuro commented Sep 19, 2017

@coveralls
Copy link

Coverage Status

Coverage remained the same at 100.0% when pulling bcabe93 on define-import-path into f259ee2 on master.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 100.0% when pulling 2a85ea9 on define-import-path into f259ee2 on master.

return err
}
return nil
return vFunc(request, traces)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These seem to be changes unrelated to this PR.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Because go vet complained

Copy link
Contributor

@vprithvi vprithvi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also, there is a typo in jaegetracing in the commit message

@@ -1,6 +1,7 @@
sudo: required

language: go
go_import_path: github.com/uber/jaeger
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

just so I'm on the same boat, why is this required?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

after the repo move the github path is going to be different, but all the imports in the code refer to uber/jaeger, so it won't build. This instruction tells Travis to relocate the repo to this path under GOPATH before building.

@yurishkuro yurishkuro changed the title Define import path in preparation of repository move to jaegetracing Define import path in preparation of repository move to jaegertracing Sep 20, 2017
@yurishkuro yurishkuro merged commit 489d7ed into master Sep 20, 2017
@yurishkuro yurishkuro deleted the define-import-path branch December 23, 2017 20:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants