Skip to content

CI: Test Linux (nightly OpenBLAS) is failing #26824

Closed

Description

@charris

See https://github.com/numpy/numpy/actions/runs/9732669831/job/26858622819. Seems to have started yesterday (6/30/2024)

Activity

  1. mattip commented on Jul 2, 2024

    @mattip
    Member

    This run is using scipy-openblas32-0.3.27.233 (aka OpenBLAS commit c33bc849a, where last week's scipy-openblas32-0.3.27.208 (aka OpenBLAS commit 1ba1b9c35) did not have this problem. @martin-frbg any thoughts?

  2. martin-frbg commented on Jul 2, 2024

    @martin-frbg

    Probably caused by that commit enforcing 0*INF=NAN to satisfy OpenMathLib/OpenBLAS#4728 . I need to doublecheck the claim made there that the reference BLAS really does this, as that change appears to introduce a significant number of LAPACK test failures on x86_64

  3. martin-frbg commented on Jul 7, 2024

    @martin-frbg

    Still haven't got a handle on this, sorry - I have convinced myself that the changes from OpenMathLib/OpenBLAS#4728 are correct, but there appears to be a problem with NAN propagation elsewhere in the code (and unrelated to the unmerged PR about NAN sort order in IMAX/IMIN, OpenMathLib/OpenBLAS#4191 ). Unfortunately I still have a hard time matching up Numpy tests with the BLAS functions they call.
    The LAPACK test failures appear to be a different issue, working around them does not change the numpy test results

  4. mattip commented on Jul 8, 2024

    @mattip
    Member

    Thanks for looking into it. Maybe we should mark the tests as xfail with that version of scipy-openblas32 to clear CI?

  5. martin-frbg commented on Jul 8, 2024

    @martin-frbg

    probably, or rollback scipy-openblas32 - I have no idea what makes more sense in your context ?
    I'll try to fix whatever this is ASAP as it is blocking the already-delayed 0.3.28, but I'd rather not revert the (valid) PR that uncovered this problem

  6. mattip commented on Jul 8, 2024

    @mattip
    Member

    We are using the "nightly sicpy-openblas" builds specifically to smoke out problems exactly like this, so it is on NumPy to mitigate the CI failure when we discover one. Sorry I cannot help right now simplifying the test to a clear OpenBLAS call.

  7. ngoldbaum commented on Jul 19, 2024

    @ngoldbaum
    Member

    I opened #26991 to temporarily allow the scipy-openblas nightly tests to fail without failing all of the CI. Just the test step in the CI job, and hopefully only temporarily.

  8. added a commit that references this issue on Aug 9, 2024
    09fef0b
  9. added a commit that references this issue on Nov 1, 2024
    f346d3f
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions