Skip to content

fix: morph failed CI recently #288

Closed

Description

@sbillinge

Problem

A morphSqueeze test failed in morph in CI here for some reason

Proposed solution

@Sparks29032 please could you take a look at this when you get a chance?

Activity

  1. Sparks29032 commented on Feb 12, 2026

    @Sparks29032
    Collaborator

    For some reason our test is checking the number of warnings thrown, which will change when any code we are interfacing is deprecated (e.g. loadData in utils). I'll put a PR when I get some time.

  2. sbillinge commented on Feb 12, 2026

    @sbillinge
    ContributorAuthor

    maybe two fixes, 1. fix the deprecations, 2. fix the check for the number of warnings unless it is needed. It probably is checking for the extrapolation warnings, so instead of checking the number of warnings, do sthg like checking that warnings are thrown with some message, sthg like that. That makes it robust against a similar failure in the future.

  3. added this to the 0.3.2 release milestone on Feb 13, 2026
  4. Sparks29032 commented on Feb 24, 2026

    @Sparks29032
    Collaborator

    Added issue #293 to fix the deprecations

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions