An error occurred while fetching the pipelines jobs.

tests passing

2 jobs for removing_chs in 49 minutes and 4 seconds (queued for 2 seconds)
Status
Job
Stage
Name
Duration
Coverage
No jobs to show
Name Stage Failure
failed
run-tests Test
FAILED kadlu/tests/geospatial/test_interpolation.py::test_can_interpolate_geotiff_data
FAILED kadlu/tests/geospatial/test_ocean.py::test_gebco_bathy - FileNotFoundE...
FAILED kadlu/tests/geospatial/test_ocean.py::test_interp_gebco_bathy - FileNo...
FAILED kadlu/tests/geospatial/test_ocean.py::test_interp_hycom_temp_gebco_bathy
FAILED kadlu/tests/geospatial/test_ocean.py::test_small_full_ocean - FileNotF...
FAILED kadlu/tests/geospatial/data_sources/test_gebco.py::test_load_bathy - F...
FAILED kadlu/tests/sound/test_geophony.py::test_transmission_loss_real_world_env
============ 7 failed, 74 passed, 26 warnings in 1926.18s (0:32:06) ============
ERROR: Job failed: exit code 1

Speed up your pipelines with Needs relationships

Using the needs keyword makes jobs run before their stage is reached. Jobs run as soon as their needs relationships are met, which speeds up your pipelines.

If you add needs to jobs in your pipeline you'll be able to view the needs relationships between jobs in this tab as a Directed Acyclic Graph (DAG).

There are no test reports for this pipeline

You can configure your job to use unit test reports, and GitLab displays a report here and in the related merge request.