[issue36684] codecov.io code coverage has not updated since 2019-04-13

Change by Inada Naoki : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___ ___ P

[issue36684] codecov.io code coverage has not updated since 2019-04-13

Inada Naoki added the comment: New changeset 87068ed00927bdeaa2ae556e4241c16cf8a845eb by Inada Naoki (Gordon P. Hemsley) in branch 'master': bpo-36684: Split out gcc and test coverage builds (GH-13146) https://github.com/python/cpython/commit/87068ed00927bdeaa2ae556e4241c16cf8a845eb ---

[issue36684] codecov.io code coverage has not updated since 2019-04-13

Change by Gordon P. Hemsley : -- pull_requests: +13059 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https:

[issue36684] codecov.io code coverage has not updated since 2019-04-13

Gordon P. Hemsley added the comment: Hah, that's indeed where I've landed in my experimentation. -- ___ Python tracker ___ ___ Pyth

[issue36684] codecov.io code coverage has not updated since 2019-04-13

Change by Inada Naoki : -- keywords: +patch pull_requests: +13018 stage: -> patch review ___ Python tracker ___ ___ Python-bugs-lis

[issue36684] codecov.io code coverage has not updated since 2019-04-13

Inada Naoki added the comment: FYI, https://github.com/python/cpython/pull/7773#issuecomment-398262396 -- nosy: +inada.naoki ___ Python tracker ___ ___

[issue36684] codecov.io code coverage has not updated since 2019-04-13

Gordon P. Hemsley added the comment: It seems the primary cause of the problem is simply that testing crossed the boundary of maximum execution time allotted by Travis CI. I'm experimenting now with ways to speed up testing without losing granularity. However, given how long code coverage ha

[issue36684] codecov.io code coverage has not updated since 2019-04-13

Gordon P. Hemsley added the comment: Testing has shown that the gcc build itself runs fine. The problem appears to be with how the coverage tests are run. -- ___ Python tracker _

[issue36684] codecov.io code coverage has not updated since 2019-04-13

Gordon P. Hemsley added the comment: I'm not sure when the gcc build started failing, but it looks like the commits at the boundary failed due to max build time. Something is apparently too slow to run. -- ___ Python tracker

[issue36684] codecov.io code coverage has not updated since 2019-04-13

Change by SilentGhost : -- components: +Build nosy: +zach.ware versions: +Python 3.8 ___ Python tracker ___ ___ Python-bugs-list mai

[issue36684] codecov.io code coverage has not updated since 2019-04-13

Gordon P. Hemsley added the comment: It looks like this may be the result of the code coverage being provided by the optional gcc build, which has been failing for quite a while. -- ___ Python tracker _

[issue36684] codecov.io code coverage has not updated since 2019-04-13

Gordon P. Hemsley added the comment: In fact, it seems the last commit on master was 962b028b0c20abcf39594f08b1e5f8c36c4e5f6f 3 months ago, which doesn't even have valid report. The previous commit, 9932a22897ef9905161dac7476e6976370e13515, was the last to have a functioning report. --

[issue36684] codecov.io code coverage has not updated since 2019-04-13

New submission from Gordon P. Hemsley : The last commit available on codecov.io is from a week ago (d28aaa7df8bcd46f4135d240d041b0b171b664cc): https://codecov.io/gh/python/cpython And the widget on the README is showing a status of "unknown". -- messages: 340588 nosy: gphemsley priori