-
-
Notifications
You must be signed in to change notification settings - Fork 18.5k
Disable codecov #27602
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
Comments
The posts it makes in PRs I usually ignore, but I've been using it to identify unused code following the Panel removal. |
We've had issues uploading codecov output from Travis recently: https://travis-ci.org/pandas-dev/pandas/jobs/574712678 |
Disabling seems like a reasonable stopgap. I didn't find anything helpful on the codecov support pages |
Although.... this may be a config issue with our CI. Note that there's no output to the command in https://travis-ci.org/pandas-dev/pandas/jobs/574509202#L2778 |
Can/should we revert #28065? Having 20-day old results on codecov is not great |
Having it enabled would be preferred, as long as it's not breaking things.
…On Tue, Sep 10, 2019 at 10:25 AM jbrockmendel ***@***.***> wrote:
Can/should we revert #28065
<#28065>? Having 20-day old
results on codecov is not great
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#27602?email_source=notifications&email_token=AAKAOIQH7M3JHUWFQ7GNRDDQI637HA5CNFSM4IG7RVM2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6LP4DQ#issuecomment-529989134>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAKAOIV4IW3YW6C4D6L7RMLQI637HANCNFSM4IG7RVMQ>
.
|
@WillAyd closable? |
re-opened, since codecov looks like it hasnt updated in 9 days |
re-closed by #30380, codecov appears back up |
I figured worth opening a dedicated issue since I've seen it come up in conversations. We don't really get a lot out of codecov right now and it tends to just be a distraction in CI. I think best to remove from CI unless anyone objects or we have a plan to better utilize
Note this would supersede #12634
The text was updated successfully, but these errors were encountered: