Skip to content

Add a JAX regression test workflow to track changes over time#3185

Open
BSnelling wants to merge 6 commits into
mainfrom
bes/jax_regression
Open

Add a JAX regression test workflow to track changes over time#3185
BSnelling wants to merge 6 commits into
mainfrom
bes/jax_regression

Conversation

@BSnelling

@BSnelling BSnelling commented Jun 16, 2026

Copy link
Copy Markdown
Collaborator

The workflow runs several representative test cases using JAX implementations and records performance metrics:

  • llh
  • number of steps
  • wall time

The workflow is scheduled to run weekly and the metrics are uploaded in json format as a workflow artefact. The intention is that these metrics will highlight if we see performance regressions in AMICI due to either src changes here or dependency updates.

Example metrics json file: https://github.com/AMICI-dev/AMICI/actions/runs/27679856537/artifacts/7691644836

@codecov

codecov Bot commented Jun 16, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 77.40%. Comparing base (e5533b3) to head (8ddf04b).

Additional details and impacted files

Impacted file tree graph

@@            Coverage Diff             @@
##             main    #3185      +/-   ##
==========================================
- Coverage   78.03%   77.40%   -0.64%     
==========================================
  Files         317      317              
  Lines       20903    20903              
  Branches     1484     1484              
==========================================
- Hits        16312    16180     -132     
- Misses       4583     4715     +132     
  Partials        8        8              
Flag Coverage Δ
cpp 71.54% <ø> (ø)
cpp_python 36.71% <ø> (ø)
petab 46.78% <ø> (ø)
petab_sciml 15.54% <ø> (ø)
python 68.30% <ø> (ø)
sbmlsuite-jax ?

Flags with carried forward coverage won't be shown. Click here to find out more.
see 4 files with indirect coverage changes

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@BSnelling BSnelling force-pushed the bes/jax_regression branch from dc10e29 to 502a046 Compare June 17, 2026 09:03
@BSnelling BSnelling marked this pull request as ready for review June 17, 2026 09:52
@BSnelling BSnelling requested a review from a team as a code owner June 17, 2026 09:52

@FFroehlich FFroehlich left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍 I would be very interested in seeing results for bigger models and across jax versions, but let’s keep that for separate PRs

name: JAX Performance Regression

on:
schedule:

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Lets also run this on PRs otherwise this can easily break e.g. when jax api version changes

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants