[BEAM-14474] Suppress 'Mean of empty slice' Runtime Warning in dataframe unit test

[Abacn]

Currently the log of python unit test results contains thousands of lines of runtime warning / future warning / deprecation warnings, making trouble shooting during development inconvenient. The most popped warning is hundreds of lines of 'RuntimeWarning: Mean of empty slice
return np.nanmean(a, axis, out=out, keepdims=keepdims)'
raised in dataframe tests, which costs > 400 lines of logs. This warning could be suppressed.

Please add a meaningful description for your change here

---

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

• Choose reviewer(s) and mention them in a comment (R: @username).
• Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
• Update CHANGES.md with noteworthy changes.
• If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

[asf-ci]

Can one of the admins verify this patch?

[asf-ci]

Can one of the admins verify this patch?

[codecov]

Codecov Report

Merging #17682 (0a93326) into master (ee5888d) will decrease coverage by 0.00%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master   #17682      +/-   ##
==========================================
- Coverage   73.99%   73.99%   -0.01%     
==========================================
  Files         695      695              
  Lines       91798    91798              
==========================================
- Hits        67927    67922       -5     
- Misses      22623    22628       +5     
  Partials     1248     1248              

Flag	Coverage Δ
python	83.73% <ø> (-0.01%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files	Coverage Δ
.../python/apache_beam/testing/test_stream_service.py	88.09% <0.00%> (-4.77%)	⬇️
...che_beam/runners/interactive/interactive_runner.py	89.20% <0.00%> (-1.44%)	⬇️
...hon/apache_beam/runners/direct/test_stream_impl.py	93.28% <0.00%> (-0.75%)	⬇️
sdks/python/apache_beam/runners/common.py	87.94% <0.00%> (-0.13%)	⬇️
...hon/apache_beam/runners/worker/bundle_processor.py	93.55% <0.00%> (ø)
sdks/python/apache_beam/utils/interactive_utils.py	97.56% <0.00%> (+2.43%)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update ee5888d...0a93326. Read the comment docs.

[Abacn]

R: @TheNeuralBit

[TheNeuralBit]

Thank you!

I think we should consider filtering these warnings in the actual implementation so they don't show up when the user is building a pipeline and we're generating a proxy. Would you mind filing a jira for that?

[TheNeuralBit]

nit: I would actually keep these where they are and just duplicate the filterwarnings calls, so that the tests are more self-contained and easy to inspect (but I'm also fine with the move if you prefer it that way)

[Abacn]

Yeah I agree with the idea. Given the amount of code added I considered pick up them into a separate helper function. Nevertheless it is still in the GroupByTest test class.

[TheNeuralBit]

Could we use a context here to make sure the filters get reset?

[Abacn]

Thanks for the suggestion. Applied.

[Abacn]

Entered BEAM-14477 for construction time warnings.