We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The DMSP ivm f18 data is not passing the pysat 3.2.0 RC tests for multi-day load.
See log in https://github.com/pysat/pysatMadrigal/actions/runs/8053868866/job/21997186424
tentative solution is to use the _new_tests flag to skip for this instrument for both RCs, then fix in the next bug release.
The text was updated successfully, but these errors were encountered:
Also:
inst_dict = {'inst_id': '', 'inst_module': <module 'pysatMadrigal.instruments.jro_isr' from '/home/runner/work/pysatMadrigal/pysat...ments/jro_isr.py'>, 'tag': 'drifts', 'user_info': {'password': 'pysat.developers@gmail.com', 'user': 'pysat+CI_tests'}} @pytest.mark.second @pytest.mark.load_options @pytest.mark.new_tests def test_load_multiple_days(self, inst_dict):
Sorry, something went wrong.
There are several other instances where flags were added with links to this issue as a TODO.
No branches or pull requests
Description
The DMSP ivm f18 data is not passing the pysat 3.2.0 RC tests for multi-day load.
To Reproduce this bug:
See log in https://github.com/pysat/pysatMadrigal/actions/runs/8053868866/job/21997186424
Test configuration
Additional context
tentative solution is to use the _new_tests flag to skip for this instrument for both RCs, then fix in the next bug release.
The text was updated successfully, but these errors were encountered: