Codecov workflow fails on every develop push: frictionless not installed

Abierto
#325 0 comentarios 0 reacciones 1 asignado Ver en GitHub

@jh-RLI ya está trabajando en esto.

Desde el 29/9/2026.

  • #324 de @jh-RLI — abierto

Evaluación

Este issue todavía no se ha evaluado.

Descripción

part: github :octocat: status: active 🚧 type: bug 🐛

Description of the issue

The "🐍 Coverage tests with codecov" workflow (.github/workflows/codecov.yml) fails on every push to develop (seen on at least 2026-07-02, 2026-09-15 and 2026-09-25 — fb7f756, 4b6390a, d0da1c0).

It installs only pytest pytest-cov pyld. Every test that imports frictionless then fails: oemetadata/v2/v21/example.py and example_modules.py import it at module level, and so do the datapackage tests.

E   ModuleNotFoundError: No module named 'frictionless'
FAILED test/oemetadata/v2/v21/test_example.py::test_oemetadata_schema_should_validate_oemetadata_example
FAILED test/oemetadata/v2/v21/test_example.py::test_oemetadata_schema_should_validate_oemetadata_example_modules
FAILED test/oemetadata/v2/v21/test_example.py::test_oemetadata_example_is_datapackage
FAILED test/oemetadata/v2/v21/test_example.py::test_oemetadata_example_modules_is_datapackage
4 failed, 78 passed

Expected: the coverage run installs the same dependencies as the test run and passes. The "🐍 Automated test" (tox) workflow is green on the same commits because it installs requirements.txt.

Steps to Reproduce

  1. Push to develop (or open the latest "🐍 Coverage tests with codecov" run on develop).
  2. Look at the "Run coverage test and create codecov" step.
  3. Four tests in test/oemetadata/v2/v21/test_example.py fail with ModuleNotFoundError: No module named 'frictionless'.

Locally: pip install pytest pytest-cov pyld && pytest --cov in a fresh env gives the same result.

Ideas of solution

  • Install requirements.txt in the codecov workflow, as tox.yml does, and pin Python 3.10 to match the test matrix. This is simple and keeps the two workflows in sync.
  • Alternative: add only frictionless jsonschema to the pip line. That's smaller, but it will break again whenever a test needs a new dependency (e.g. rdflib for graph.py).

The first option is implemented in #324.

Context and Environment

  • Version used: develop @ d0da1c0
  • Operating system: GitHub Actions ubuntu-latest
  • Environment setup and (python) version: actions/setup-python@v5 without a version (runner default); reproduced locally with Python 3.10.12

Workflow checklist

Lenguaje dominante
Python
Estrellas
26
Forks
4
Métricas de merge de PR
Sin PR fusionados en 30 d

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de OpenEnergyPlatform/oemetadata

Todos los issues de OpenEnergyPlatform/oemetadata

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.