Log file Viewer

[15:35:25] <toad_polo> pradyunsg: (or anyone): Do you happen to know if there's some special magic invocation I can do to make gcov work with PEP 518 build isolation?

[15:36:36] <toad_polo> Digging into it a bit, it seems like if I build with CFLAGS="--coverage" with `pip install -e .`, it will generate coverage files in the build/ directory.

[15:37:38] <toad_polo> If I don't do an editable install, I'm guessing that build directory is some random temporary directory that is cleared before I run pytest anyway.

[15:57:05] <toad_polo> Ahah, progress! GCOV_PREFIX helps.

[16:08:06] <toad_polo> Hmm, no, I'm wrong.

[16:08:12] <toad_polo> I have no idea how to do this.

[18:05:02] <toad_polo> I may have to use `usedevelop` or a direct `setup.py` invocation to get C coverage data, at least to start with.

[18:05:39] <toad_polo> I am not sure if this is a problem with `gcovr`, with my inadequate understanding of how to configure gcov, with PEP 517 or with the tox workflow.

[18:57:30] <toad_polo> It seems like gcov really hates the idea of moving the entire directory to an ephemeral build location.

[19:00:24] <toad_polo> I hacked something in to my setup.py file to retrieve the gcno file and it actually seemed like it was going to work, but alas it seems to have the absolute path of the source files hard coded in to the code coverage.

[19:02:57] <toad_polo> Seriously, no joke.

[19:03:17] <toad_polo> It's really hard to concentrate with this tantalizingly close.

[19:36:47] <toad_polo> Weird, I managed to get it to actually output the correct stuff, but it spews `.gcov` files all over my current directory, and complains about not being able to find a bunch of files.

[19:38:48] <toad_polo> Oh hey, deleting my `.tox` and re-creating it fixed al the warnings. Still a bunch of `.gcov` files everywhere, but I can probably fix that as well.