ignore warnings in hera_cal and hera_qm test runs

[bhazelton]

Description

To make it easier to see the actual errors. This only ignores warnings that are not coming from pyuvdata.

Motivation and Context

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation change (documentation changes only)
• Version change
• Build or continuous integration change

Checklist:

• I have read the contribution guide.
• My code follows the code style of this project.

Build or continuous integration change checklist:

• If required or optional dependencies have changed (including version numbers), I have updated the readme to reflect this.
• If this is a new CI setup, I have added the associated badge to the readme and to references/make_index.py (if appropriate).

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (7b5333f) 99.92% compared to head (9246a97) 99.92%.
Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1402   +/-   ##
=======================================
  Coverage   99.92%   99.92%           
=======================================
  Files          37       37           
  Lines       20766    20766           
=======================================
  Hits        20750    20750           
  Misses         16       16           

---

Continue to review full report in Codecov by Sentry.

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

[steven-murray]

Hmmm, maybe we should be more selective in what warnings are ignored. The warnings docs say that the warnings format is:

action:message:category:module:line

We probably want to only capture DeprecationWarning from pyuvdata? So:

-W ignore,default::DeprecationWarning:pyuvdata

[bhazelton]

Thanks! I backed it off some to only ignore non-pyuvdata warnings. I didn't limit to only pyuvdata Deprecation Warnings because we've broken hera_qm before with new pyuvdata user warnings because of the warning testing in hera_qm.

I tested this on my machine by adding a new warning and it worked.

[steven-murray]

Great!