[ 
https://issues.apache.org/jira/browse/BEAM-10701?focusedWorklogId=475406&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-475406
 ]

ASF GitHub Bot logged work on BEAM-10701:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 27/Aug/20 16:38
            Start Date: 27/Aug/20 16:38
    Worklog Time Spent: 10m 
      Work Description: saavannanavati commented on pull request #12696:
URL: https://github.com/apache/beam/pull/12696#issuecomment-682060896


   Ooh yeah nice catch, `"*.py::sdks/python/"` is a catch-all.
   
   > Why doesn't this tool just record the paths relative to the repo?
   
   Let me open a support ticket with Codecov because that seems like the 
logical approach they should be taking.
   
   Btw, any idea why the YAML isn't showing up in the `Build` section of any of 
the Codecov commits? 
[Example](https://codecov.io/gh/apache/beam/commit/d5201cfb96ff4ac1299f8741a0f6cbdba2ac05ec/build)


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]


Issue Time Tracking
-------------------

    Worklog Id:     (was: 475406)
    Time Spent: 5h  (was: 4h 50m)

> Add Codecov YAML
> ----------------
>
>                 Key: BEAM-10701
>                 URL: https://issues.apache.org/jira/browse/BEAM-10701
>             Project: Beam
>          Issue Type: Improvement
>          Components: sdk-py-core
>            Reporter: Saavan Nanavati
>            Priority: P2
>          Time Spent: 5h
>  Remaining Estimate: 0h
>
> This will fix path resolution errors and allow the code coverage reports to 
> successfully upload to Codecov.
>  
> The reports can be seen at the following URL: 
> [https://codecov.io/gh/apache/beam]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to