GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — Update libraries we test on CI · Issue #235 · data-apis/array-api-tests

Update libraries we test on CI #235

New issue
Copy link
New issue
Copy link
Open
Open
Update libraries we test on CI#235
Copy link
Labels
tracking

Description

@honno
honno
opened on Feb 20, 2024
Issue body actions
  • Firstly we really need to
    • Replace numpy.array_api with array-api-strict
      • numpy.array_api is going to be removed and supplanted by this third-party library
      • As bought up in More improvements to test_linalg #101 (comment)
    • Also cover meta/ tests (we never did before!)
      • Would require one or two fixes of those tests.
    • Cover different ARRAY_API_TESTS_VERSION values too
      • Support for older versions of the standard array-api-strict#8 would be handy here
  • Then ideally we're testing libraries covered by array-api-compat
    • NumPy
    • PyTorch
    • Dask
    • CuPy is probably a no-go because GPUs on CI is too finnicky
  • I think it'd be really nice to test jax.experimental.array_api too as it has some distinct properties that we want to be mindful with for future test suite development.

Activity

  1. honno
    added
    tracking
    on Feb 20, 2024
  2. asmeurer commented on Mar 21, 2024

    @asmeurer
    asmeurer
    on Mar 21, 2024
    Member
    More actions

    For array-api-compat I have a script that I can run on a CUDA machine that runs the CuPy tests. We could have something like that here. We could also do that for PyTorch GPU. We would then just have to run it ourselves manually from time to time.

    Reacted by Matthew Barber
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

    tracking

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      You are visitor 01402520 — GeezerVison does not store the pages you look up.
      Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.