You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The partial-matching workflow leads to errors, even if those issues occur in other packages, where we cannot control the behaviour (e.g. https://github.com/easystats/insight/actions/runs/9677160242/job/26698218779?pr=897). This makes (some?) workflows essentially useless. If a failing example is quite at the beginning of this workflows, most of the remaining examples will never be checked. And we cannot "fix" this, because the partial-matching happens in other packages.
Workflows on R <= 4.3 fail since weeks. I think we should at least temporarily disable those workflows. I never look into these errors, because I'm expecting it's the old failure that is not related to my changes. So I will never realize if this workflow is working again and failures are indeed to my changes, because I'm ignoring those workflows right now.
The partial-matching workflow leads to errors, even if those issues occur in other packages, where we cannot control the behaviour (e.g. https://github.com/easystats/insight/actions/runs/9677160242/job/26698218779?pr=897). This makes (some?) workflows essentially useless. If a failing example is quite at the beginning of this workflows, most of the remaining examples will never be checked. And we cannot "fix" this, because the partial-matching happens in other packages.
Workflows on R <= 4.3 fail since weeks. I think we should at least temporarily disable those workflows. I never look into these errors, because I'm expecting it's the old failure that is not related to my changes. So I will never realize if this workflow is working again and failures are indeed to my changes, because I'm ignoring those workflows right now.