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
Tweak codecov config #240
Labels
Area: Infrastructure
Pertains to project infrastructure (e.g. CI, linting)
Type: Enhancement
Enhancement to existing functionality
Comments
dopplershift
added
Area: Infrastructure
Pertains to project infrastructure (e.g. CI, linting)
Type: Enhancement
Enhancement to existing functionality
labels
Oct 31, 2016
dopplershift
added a commit
to dopplershift/MetPy
that referenced
this issue
Nov 21, 2016
This should fix codecov staying in pending state on failed builds (Fixes Unidata#240)
dopplershift
added a commit
to dopplershift/MetPy
that referenced
this issue
Nov 21, 2016
Also explicitly configure codecov to report status in event of CI failure. This should fix codecov staying in pending state on failed builds (Fixes Unidata#240)
dopplershift
added a commit
to dopplershift/MetPy
that referenced
this issue
Nov 21, 2016
Also explicitly configure codecov to report status in event of CI failure. This should fix codecov staying in pending state on failed builds (Fixes Unidata#240)
dopplershift
added a commit
to dopplershift/MetPy
that referenced
this issue
Nov 21, 2016
Also explicitly configure codecov to report status in event of CI failure. This should fix codecov staying in pending state on failed builds (Fixes Unidata#240)
dopplershift
added a commit
to dopplershift/MetPy
that referenced
this issue
Nov 21, 2016
Also explicitly configure codecov to report status in event of CI failure. This should fix codecov staying in pending state on failed builds (Fixes Unidata#240)
dopplershift
added a commit
to dopplershift/MetPy
that referenced
this issue
Nov 23, 2016
Also explicitly configure codecov to report status in event of CI failure. This should fix codecov staying in pending state on failed builds (Fixes Unidata#240)
ShawnMurd
pushed a commit
to ShawnMurd/MetPy
that referenced
this issue
Dec 1, 2016
Also explicitly configure codecov to report status in event of CI failure. This should fix codecov staying in pending state on failed builds (Fixes Unidata#240)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Area: Infrastructure
Pertains to project infrastructure (e.g. CI, linting)
Type: Enhancement
Enhancement to existing functionality
It's really irritating that when Travis fails (even though it might not be due to a test with coverage failing) it causes codecov.io to not report a status. We should adjust the config to solve this.
The text was updated successfully, but these errors were encountered: