relative_files & include broken since 7.0

[ikonst]

Describe the bug

1. Create simple test case with relative_files = true

   mkdir foo
   echo 'print()" > foo/bar.py
   echo "[run]\nrelative_files = true" > .coveragerc

2. coverage run foo/bar.py

3. coverage report --include=foo/bar.py

Expected (as behavior was before 7.0):

Name         Stmts   Miss  Cover
--------------------------------
foo/bar.py       1      0   100%
--------------------------------
TOTAL            1      0   100%

Actual:

No data to report

Additional analysis:

It appears that the regex created from the foo/bar.py glob pattern includes the current working directory, which might explain why it wouldn't match against relative paths anymore.

[nedbat]

Hmm, I see what you mean. It will still work if you use --include='*/foo/bar.py'.

[ikonst]

BTW, regarding --include='*/foo/bar.py':

1. Would that get me more than I bargained for, e.g. also spam/foo/bar.py?
2. Is it compatible with 6.x?

[nedbat]

I have a possible fix, but it's hard to work through all the permutations. I will investigate.

[nedbat]

@ikonst do you need to use the same settings file for both coverage 6.x and 7.x?

[ikonst]

Preferably, since I have a script invoke that report across repositories where different versions might be used. Also, I think the current syntax is intuitive for the relative files case.

[marcgibbons]

@marcgibbons at PyCon 23

[marcgibbons]

Also, looks like #1571 is a duplicate.

[nedbat]

This is fixed in ee6506f.

[nedbat]

This is now released as part of coverage 7.2.4.