Skip to content
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

update travis build to go 1.12 #284

Merged
merged 1 commit into from
Jun 11, 2019
Merged

update travis build to go 1.12 #284

merged 1 commit into from
Jun 11, 2019

Conversation

ryanking
Copy link
Contributor

Test Plan

  • travis-ci

References

@ryanking ryanking requested a review from a team as a code owner June 11, 2019 22:30
@codecov
Copy link

codecov bot commented Jun 11, 2019

Codecov Report

Merging #284 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #284   +/-   ##
=======================================
  Coverage   80.04%   80.04%           
=======================================
  Files          17       17           
  Lines        1408     1408           
=======================================
  Hits         1127     1127           
  Misses        160      160           
  Partials      121      121

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update be10ec9...f0333e4. Read the comment docs.

@czimergebot czimergebot merged commit 581fe92 into master Jun 11, 2019
@ryanking ryanking deleted the ryanking/go-1.12 branch March 9, 2020 22:30
palasha pushed a commit to palasha/fogg that referenced this pull request Apr 7, 2020
update travis build to go 1.12
### Test Plan
* travis-ci

### References
@vincenthsh vincenthsh mentioned this pull request Nov 12, 2024
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.

3 participants