No. That is the plan. Petsc's script gcov.py works correctly and we need to move it to codecov.io.
--Junchao Zhang On Thu, Jun 25, 2020 at 9:34 AM Aagaard, Brad T via petsc-dev < [email protected]> wrote: > Are you opposed to using codecov.io to compile the results and generate > plots? > > Brad > > On 6/24/20, 4:17 PM, "petsc-dev on behalf of Scott Kruger" < > [email protected] on behalf of [email protected]> wrote: > > > > For more detail, Stage 4 of the pipeline ("analyze-pipeline") has all > of > the gcov data and you can download it from the right side after > clicking > "Download" from "Job Artifacts" tab. This is handled by the > .gitlab-ci.yml file (search for gcov). > > If someone knows how gcov outputs it's data and how to upgrade the > lib/petsc/bin/maint/gcov.py to read in the data as gitlab organizes it > and then output the html/figures, then we'd have it done (locally. To > upload to wiki or other gitlab display would require more work on the > gitlab-ci.yml file). > > I spent quite a few hours on it, and got stuck. It requires > understanding gcov to a degree that was interfering with other > priorities. > > If someone has the knowledge or inclination, it's a good problem to > solve. > > Scott > > > > On 6/24/20 2:39 PM, Satish Balay via petsc-dev wrote: > > Its not yet setup in the current CI > > > > Satish > > > > On Wed, 24 Jun 2020, Matthew Knepley wrote: > > > >> Thanks, > >> > >> Matt > >> > >> > > -- > Tech-X Corporation [email protected] > 5621 Arapahoe Ave, Suite A Phone: (720) 974-1841 > Boulder, CO 80303 Fax: (303) 448-7756 > >
