[FEA] cudf_kafka: add unit tests about cudf HOT 3 OPEN

@jameslamb Last time this topic came up we concluded not to produce cudf_kafka wheels. There are very few consumers of this library, and at that point, the build system would have required us to build and ship all of libcudf as part of both the cudf-cu(11|12) and cudf_kafka-cu(11|12) wheel if we chose to produce one. Perhaps the new C++ wheels for libcudf would solve part of this problem (building and shipping less in the Python wheels) but we'd probably need libcudf_kafka wheels in addition to libcudf wheels. This would be pretty complicated for very little gain, given the low usage of this library.

I am inclined to add unit tests that are as minimal as possible for conda packages and not ship cudf_kafka wheels at all. That would split the scope of this issue: add unit tests 👍 , add wheels 👎.

References:

• #14292 (comment)
• #14292 (comment)
• #14292 (comment)

from cudf.

Ah!!!

@bdice I didn't realize that we weren't shipping cudf_kafka wheels. I definitely did not mean for this issue to propose doing that! My fault for assuming and not checking more closely 🙈

I'll modify the title and description to reflect that this is only about adding tests for the conda package.

as minimal as possible

100%, my main motivation for this was wanting a test to confirm that cudf_kafka.__version__ is populated and available. I'm not proposing going any further than that.

from cudf.

Agree with what Bradley said: yes to tests, no to wheels.

from cudf.