Codecov workflow fails on every develop push: frictionless not installed

Aperta
#325 0 commenti 0 reazioni 1 assegnatario Vedi su GitHub

@jh-RLI ci sta già lavorando.

Dal 29/9/2026.

  • #324 di @jh-RLI — aperta

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

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

Lingua principale
Python
Stelle
26
Fork
4
Metriche di merge delle PR
Nessuna PR unita negli ultimi 30g

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di OpenEnergyPlatform/oemetadata

Tutte le issue di OpenEnergyPlatform/oemetadata

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.