Skip to content

CI failures do to wrong caching of venv #69

@CloseChoice

Description

@CloseChoice

We cache the venv in the github setup workflow (in order to not have to set it up again for every catalog), but this causes problems when there is already a cached version and the setup step runs.

The current workaround is just to delete the cached version from the github caches.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions