Skip to content

Do terrible things to make go1.10 coverage reports work #48

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Apr 18, 2018

Conversation

prateek
Copy link
Collaborator

@prateek prateek commented Apr 18, 2018

More details about why can be found here: golang/go#23883

Copy link
Collaborator

@jeromefroe jeromefroe left a comment

Choose a reason for hiding this comment

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

¯_(ツ)_/¯

@prateek prateek merged commit 473aa7b into master Apr 18, 2018
@prateek prateek deleted the prateek/go1.10-coverage-hack branch April 18, 2018 23:46
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.

2 participants