v2.0.2 lcov.info absolute paths now incorrectly translated to relative paths

[tande35006]

Updated from karma-coverage 2.0.1 to 2.0.2 and the paths in the lcov.info are now being translated to relative paths. Using sonarcloud.io for coverage analysis which doesn't support the relative paths.

v2.0.1 lcov.info file:

v2.0.2 lcov.info file now produces:

sonarcloud log:

[anthony-redFox]

@tande35006 try to use relativePath: false for lcov report

[gingemonster]

anyone got this working, not 100% sure where the "relativePath: false" flag should be set? I assume in karma.config.js so I tried a few places and none seem to work. Where should it go?

coverageReporter: {
  reporters: [ 
    { type: 'html' },
    { type: 'lcovonly', file: '../../../../lcov.info' },
    { type: 'text-summary' },
    { type: 'teamcity' }
  ],
  dir: path.resolve(__dirname, 'coverage-karma'),
  subdir: '.',
},

[anthony-redFox]

sorry, it is my mistake. it is issue istanbuljs/istanbuljs#529

you can define projectRoot for project and should be resolved

[moussetc]

@anthony-redFox

sorry, it is my mistake. it is issue istanbuljs/istanbuljs#529

you can define projectRoot for project and should be resolved

Hi, I'm struggling with this issue and I don't see how to define this projectRoot option with Karma. Could you provide a karma.conf example that generates absolute path with karma-coverage >= 2.0.2?