Coverage is still messed up

(Bill Lorensen) #1

Foks,

Coverage is running but not reporting file coverage.

Bill

(Ben Boeckel) #2

Looking at the buildbot logs, I see this:

Error(s) while accumulating results:
  Looks like there are more lines in the file: /home/kitware/dashboards/buildbot/vtk_nightly-master-ike-linux-shared-release_coverage_mpi_nightly_python2/source/Common/Core/vtkSimpleCriticalSection.cxx
  Looks like there are more lines in the file: /home/kitware/dashboards/buildbot/vtk_nightly-master-ike-linux-shared-release_coverage_mpi_nightly_python2/source/Common/Core/vtkTimeStamp.cxx

which might be throwing a wrench into the file-level coverage data. Anyone know what this means? @brad.king?

There are 48 coverage.xml files uploaded however, so I assume the file-level data is in there somewhere. Maybe CDash has a bug?

(Ben Boeckel) #3

I talked with Zack here and he’s going to look at it.

(Ben Boeckel) #4

He says the CDash side is fixed. Not sure what’s up with ike itself right now. I’ve started a coverage build manually to see if it just needs to run again.

Edit to add: Seems to work now: https://open.cdash.org/viewCoverage.php?buildid=5846221