Skip to content

CI: trigger stormpy tests after changes in Storm #911

@volkm

Description

@volkm

After commits to master, we should also trigger stormpy in the future to catch incompatibilities between Storm and stormpy as soon as possible.
But let's first restructure the CI in #892 before extending it with this idea.

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