Use test paths relative to package directory.

[bdice]

Description

This PR standardizes how our test paths are defined for dask-cudf and custreamz. This was originally a test to investigate a question related to CodeCov, which is answered below. We noticed that some coverage reports in the CI outputs used full paths like /opt/conda/envs/test/lib/python3.10/site-packages/cudf/__init__.py while other coverage reports gave relative paths like cudf/__init__.py. The net result of this PR is that coverage reports are unchanged, but our CI tests are more correct because they always pull from the installed packages rather than the local packages (import dask_cudf is fetching the built conda packages from site-packages and not importing from the current path in the cloned repo).

Checklist

• I am familiar with the Contributing Guidelines.
• New or existing tests cover these changes.
• The documentation is up to date with these changes.

[bdice]

@ajschmidt8 I think the absolute paths must be interpreted correctly by CodeCov. In commit 002fba0, I changed the test paths but forgot to modify the path to .coveragerc. Then in commit 689e67e, I fixed that problem and the total coverage is unchanged relative to the base branch. I would like to merge this PR since it makes our path handling more standard across packages and adds a missing .coveragerc file for custreamz.

[galipremsagar]

@bdice Should we wait for codecov bot to comment the reports on this PR before merging?

[bdice]

@bdice Should we wait for codecov bot to comment the reports on this PR before merging?

I don't know why the bot hasn't commented yet. I will merge in branch-23.04 and see if a new commit triggers the bot since I opened this PR from draft.

[bdice]

Hard to know what's wrong. @galipremsagar Can you tell? https://app.codecov.io/gh/rapidsai/cudf/pull/12751

[galipremsagar]

Hard to know what's wrong. @galipremsagar Can you tell? https://app.codecov.io/gh/rapidsai/cudf/pull/12751

The error shown in that page that base branch is missing is related to our nightly jobs not running probably.

But the bot should have commented even if above is the case, lets wait and see if the bot comments in a bit.

[ajschmidt8]

The error shown in that page that base branch is missing is related to our nightly jobs not running probably.

For reference, we generally don't enable nightly builds/tests for the next development branch until the release is complete.

So 23.04 nightly builds/tests will begin next week.

[ajschmidt8]

I still don't get why in some coverage results (like this), it reports relative paths like:

kafka.py 

but in that same log (here), it shows other paths absolutely like:

/opt/conda/envs/test/lib/python3.10/site-packages/cudf/core/buffer/utils.py

[bdice]

/merge

[vyasr]

@bdice were the above issues with the codecov bot resolved?

[bdice]

@vyasr I don't see Codecov bot PR comments on these recent PRs, so it's not related to the changes in this PR (which seemed fine, I verified them).

• Use python -m pytest for nightly wheel tests #12871
• Split C++ and Python build dependencies into separate lists. #12724

I don't know how to address this, it probably takes repo admin privileges if it's an issue with the application setup or webhooks. cc: @rapidsai/ops