Skip to content

Some of molecular atmosphere tests are failing

Summary

3 out of 8 tests for molecular atmosphere are failing.

Steps to reproduce

Run pytest from the project root. Note: you have to fix the relative import first, otherwise all tests will fail. Option: use feature/db-integration branch where it is fixed, until it is merged

What is the expected correct behavior?

All tests should pass. CI test job, that is currently allowed to fail, should not be allowed to fail.

Relevant logs and/or screenshots

Relevant errors:

FAILED calibpipe/tests/test_molecular_atmosphere_calibrator.py::TestMolecularAtmosphere::test_grib2_conversion - AssertionError: Tool returned with error status 1
FAILED calibpipe/tests/test_molecular_atmosphere_calibrator.py::TestMolecularAtmosphere::test_macobac - FileNotFoundError: [Errno 2] No such file or directory: '/Users/mdalchen/work/dpps/code/code-prototypes/calibpipe/data/atmosphere/molecular_atmosph...
FAILED calibpipe/tests/test_molecular_atmosphere_calibrator.py::TestMolecularAtmosphere::test_non_valid_gdas_request - OSError: pytest: reading from stdin while output is captured!  Consider using `-s`.

Environment

  • Version used: commit 87fd710c
  • Operation System: OS X, env according to dev instructions

The second failed test fails due to the absence of a test file The third test fails due to the expectation of input from CLI. The test (service) credentials for GDAS must be created and passed to the pipeline through GitLab secure variables.