Should consider using pkg/errors

[shawn-hurley]

We should consider using the errors package to wrap errors and keep the context of errors as they are bubbled up.

I would actually suggest moving to https://github.com/pkg/errors for this kind of thing. It is very useful. Has a method
errors.Wrap(err,"some additional context")
that returns an error. It also provides the benefit of providing stack traces when the errors are logged with %+v

@maleck13 suggested this while commenting on #716

I think a simple proposal of how this would be used, and how we would go about adding it to our codebase is something that should be considered.

[maleck13]

I have used this package many times. It has a small footprint but provides great value.

[eriknelson]

I think a simple proposal of how this would be used, and how we would go about adding it to our codebase is something that should be considered.

Sounds good to me. I would prefer not to have to manually wrap errors all the time; some sugar to make this simple would be my desire.

Love the stack traces!

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[jmrodri]

/close

[openshift-ci-robot]

@jmrodri: Closing this issue.

In response to this:

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[jmrodri]

/close