pants question when running `test pytest` tests and looking Pants #general

pants question: when running `test.pytest` tests ...

fast-author-5112

10/22/2019, 9:21 PM

pants question: when running

test.pytest

tests and looking at the coverage generated i see that several files are referenced through

.pants.d/pyrep/sources/

cache locations instead of their actual paths in our codebase. does anyone know why this happens? when combining coverage results for viewing in sonarqube all of those files are ignored with logs saying they no longer exist. any input would be appreciated

aloof-angle-91616

10/22/2019, 10:12 PM

i might also ask in #lang-python if nobody bites in this channel

aloof-angle-91616

10/22/2019, 10:13 PM

it looks like this is a bug but i’m pretty sure we use the same coverage in the pants repo and i’m pretty sure we don’t have this problem, but have not personally interacted with python coverage yet

happy-kitchen-89482

10/22/2019, 11:17 PM

We have some code that rewrites those locations to the actual ones, so this sounds like a bug

fast-author-5112

10/23/2019, 3:48 PM

where can i file a bug for this? we are actively using code coverage to interface with sonarqube and would be very helpful for us if it was fixed

aloof-angle-91616

10/23/2019, 4:51 PM

https://github.com/pantsbuild/pants/issues/new!

aloof-angle-91616

10/23/2019, 4:52 PM

this particular bug may actually lie in pex which handles code coverage i think but the pants repo is still the right place to put the issue for things that are breaking pants

fresh-architect-74417

10/23/2019, 10:23 PM

I have a custom script that replace random pex coverage location with the real one 😄

enough-analyst-54434

10/23/2019, 10:24 PM

Nack to the above. Pants handles code coverage seperately from PEX. It happens to run tests via pex, but that is all.

4 Views

Open in Slack

Previous Next